IDP 4.3 and non URL SP entity IDs

Ullfig, Roberto Alfredo rullfig at uic.edu
Thu Jan 19 14:28:40 UTC 2023


I noticed a new piece of SAML being sent. Example:

    <saml2p:Scoping>
        <saml2p:RequesterID>box.net</saml2p:RequesterID>
    </saml2p:Scoping>

that wasn't there before and Microsoft's IDP doesn't like the fact that box.net is not in URL format:

AADSTS7500522: XML element 'RequesterID' in XML namespace 'urn:oasis:names:tc:SAML:2.0:protocol' in the SAML message must be a URI.

What is adding that Scoping section? This is in the initial request:

<saml2p:AuthnRequest xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol"...

Our IDP is proxying to an Azure IDP. Thanks!

---
Roberto Ullfig - rullfig at uic.edu
Systems Administrator
Enterprise Applications & Services | Technology Solutions
University of Illinois - Chicago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230119/32cec24f/attachment.htm>


More information about the users mailing list