<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p>On 3/4/25 4:35 PM, Janemarie Duh via users wrote:</p>
<blockquote type="cite"
cite="mid:CADt-A4_m4SoiUOo_9vt-w0beNAQKUMQpZMxV4L0GtsdME0P_+Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">To refresh memories, the strict default was new
with IdPv5:
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<p class="gmail-p1"
style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;font-size:14px;line-height:normal;font-family:Helvetica"><span
class="gmail-s1" style="font-kerning:none">The XML
processing code in OpenSAML has been enhanced to support a
more strict form of processing that rejects
unexpected/unknown XML Attributes, Elements, and even
stray characters inside elements. Older versions tended to
ignore them. In the vast majority of cases, rejecting such
content is desirable but it is possible to turn off this
processing mode by setting the property <b>opensaml.config.xml.unmarshall.strictMode</b>
to “false”. Note that this setting appears to reject
otherwise valid metadata produced by Microsoft products
(see Known Bugs).</span></p>
</blockquote>
</div>
</blockquote>
<p><br>
</p>
<p>Your issue doesn't have anything to do with this new setting.
That's about "unknown" XML attributes, elements and element
content which isn't specified in the relevant XML schemas. That's
at a much higher level of XML processing than your error...<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CADt-A4_m4SoiUOo_9vt-w0beNAQKUMQpZMxV4L0GtsdME0P_+Q@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>Their ACS url looks like this:</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <a
href="https://uofdepd.evidence.com/?class=UIX&proc=Login"
moz-do-not-send="true">https://uofdepd.evidence.com/?class=UIX&proc=Login</a></blockquote>
<div><br>
</div>
<div>Upon restarting Jetty, errors appear because the xml parser
sees "proc" as unexpected content and thinks a semicolon
delimiter is required after it. </div>
</div>
</blockquote>
<p><br>
</p>
<p>Your error is that literal '&' characters aren't allowed in
XML, period. The '&' is a special reserved character used to
represent an 'entity', which is sort of like a macro that is
replaced at parse time. An entity always terminates with a ';',
and it's not seeing a terminating ';',. So that's literally what
it is complaining about. It's fundamentally invalid XML. This is a
very low-level XML parsing error, nothing to do with Shibboleth
software choices, etc.</p>
<p>For the correct way, see the wiki, which happens to have the
correct example for your exact ACS issue:</p>
<p><a class="moz-txt-link-freetext" href="https://shibboleth.atlassian.net/wiki/spaces/CONCEPT/pages/928645443/MetadataCorrectness#MetadataCorrectness-EncodingofSpecialCharacters">https://shibboleth.atlassian.net/wiki/spaces/CONCEPT/pages/928645443/MetadataCorrectness#MetadataCorrectness-EncodingofSpecialCharacters</a><br>
</p>
<br>
</body>
</html>