Skip to content
This repository has been archived by the owner on Dec 16, 2020. It is now read-only.

Service wants persistent nameID, but metadata asks for transient (and others) #4

Open
lhoekenga opened this issue May 16, 2017 · 0 comments

Comments

@lhoekenga
Copy link

DefaultSAMLUserDetailsService.java appears to be looking for either "urn:mace:dir:attribute-def:eduPersonTargetedID" or "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent", but the generated metadata includes non-preferred formats:

    <md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</md:NameIDFormat>
    <md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</md:NameIDFormat>
    <md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</md:NameIDFormat>
    <md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat>
    <md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName</md:NameIDFormat>

Can be fixed on the IDP side by removing the signature and adjusting the NameIDFormats by hand, but consider removing the unwanted / unneeded NameIDFormat elements from the generated metadata.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant