<div dir="ltr">Yeah, that makes some sense, since the rest of their metadata isn't so afflicted, it's just the certificate data. Even if we ultimately have to accommodate their broken(?) metadata, it would be personally satisfying to be able to tell them, "nuh uh".</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 23, 2022 at 2:24 PM IAM David Bantz via users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div dir="ltr">
I wonder whether those line termination characters were added in the process of transmitting or intermediate storage of the data.</div><div dir="ltr"><br></div><div dir="ltr"><br><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On 23Mar2022 at 16:01:40, Baron Fujimoto <<a href="mailto:baron@hawaii.edu" target="_blank">baron@hawaii.edu</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex" type="cite">
<div dir="ltr">We are working with an SP who is providing metadata where the character entity "
" (carriage return, I believe) has been appended to each line of their x509 certificates . E.g.:<div><br></div><font face="monospace"> <ds:X509Data><br></font><div><font face="monospace"> <ds:X509Certificate>MIIGXTCCBUWgAwIBAgIQCLgQc9Z8Mn06Q0tiGbaLyjANBgkqhkiG9w0BAQsFADBZMQswCQYDVQQG<font color="#741b47">
</font><br></font></div><div><font face="monospace">EwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMTMwMQYDVQQDEypEaWdpQ2VydCBHbG9iYWwgRzIg<font color="#741b47">
</font><br>...<br>3H8TzSiVX+JruLLaUdWCtTqKDYyVJBxNNKV/cVzLqcXaLIUq3LwqrSLfh1axuYW64VT1SHe2MAsM<font color="#741b47">
</font><br>U7U1sUyCVwFp2Z7D3xnz+erklZPsBxecF7mTebgi9XUUUJDiEA==</ds:X509Certificate><br></font></div><div><font face="monospace"> <ds:X509Data></font><br></div><div><br></div><div>The IdP fails to parse this. Is this actually valid SAML for the metadata? I couldn't find a standards reference that answered this definitively. The SP is claiming that, "Since we include the "
" characters to show a break in the metadata information, we will not be able to remove these characters from the XML file" and advises, "If Shibboleth cannot parse the metadata correctly..." we need to download and manually fix the metadata ourselves. If their metadata is in fact not standards compliant, I would very much appreciate any references I could provide to the SP to demonstrate that.<br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Baron Fujimoto <<a href="mailto:baron@hawaii.edu" target="_blank">baron@hawaii.edu</a>> :: UH Information Technology Services<br>minutas cantorum, minutas balorum, minutas carboratum desendus pantorum</div></div></div></div>
<div>
<div>
-- <br>For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw" target="_blank">https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
</div>
</div>
</blockquote>
</div>
</div></div>
-- <br>
For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw" rel="noreferrer" target="_blank">https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Baron Fujimoto <<a href="mailto:baron@hawaii.edu" target="_blank">baron@hawaii.edu</a>> :: UH Information Technology Services<br>minutas cantorum, minutas balorum, minutas carboratum desendus pantorum</div></div>