IDP 4.1.5 Nameid

[Mathew, Sunil]

Thanks Scott.

I followed the example here: http://shibboleth.net/pipermail/users/2021-January/048839.html and I modified saml-nameid.xml to the following:

        <bean parent="shibboleth.SAML2AttributeSourcedGenerator"

            p:omitQualifiers="true"

            p:format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"

            p:attributeSourceIds="#{ {'canvas_name_id'} }" />

and atttibute-resolver.xml to the following:
    <AttributeDefinition xsi:type="PrincipalName" id="canvas_name_id">
        <AttributeEncoder xsi:type="SAML1String" name="canvas_name_id" encodeType="false" />
        <AttributeEncoder xsi:type="SAML2String" name="canvas_name_id" encodeType="false" />
    </AttributeDefinition>

Does that mean if I have to define nameids for each SP, I will have to configure separate SAML2AttributeSourcedGenerator in saml-nameid.xml?

Regards,
Sunil


From: Cantor, Scott <cantor.2 at osu.edu>
Date: Friday, March 18, 2022 at 10:54 AM
To: Shib Users <users at shibboleth.net>
Cc: Mathew, Sunil <smathew at hbs.edu>
Subject: Re: IDP 4.1.5 Nameid
There is no "legacy" feature to document, it was removed, that's why it causes warnings in the later 3.x releases. The documentation on NameID Generation is very prominent in the wiki (that's what it's called). It worked in 3.x largely the same way.

-- Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220318/ab2738da/attachment.htm>