hello
based on
https://wiki.shibboleth.net/confluence/display/IDP4/NameIDGenerationConfiguration
I did manage to create a persistent nameID based on mail attribute as
required by specific SPs [1]
but there are other SPs that needs also a persistent nameID, this time
based on eppn !
I can I mix those 2 (and perhaps one day 3 or more ... ) attribute based
persistent NameIDs for differents SPs [2] ?
in /saml-nameid.properties/ there's only on variable :
////idp.persistentId.sourceAttribute//
Thanks .
[1]
/saml-nameid.properties//
/
/idp.persistentId.useUnfilteredAttributes = true//
//idp.persistentId.sourceAttribute = mail//
//idp.persistentId.generator = shibboleth.ComputedPersistentIdGenerator//
//
/
/saml-nameid.xml//
/
/ <ref bean="shibboleth.SAML2TransientGenerator" />//
//
// <!-- Uncommenting this bean requires configuration in
saml-nameid.properties. -->//
// <!-- Jehan -->//
// <ref bean="shibboleth.SAML2PersistentGenerator" />//
// <bean parent="shibboleth.SAML2AttributeSourcedGenerator"//
// p:omitQualifiers="true"//
//p:format="urn:oasis:names:tc:SAML:2.0:nameid-format:emailAddress"//
//* p:attributeSourceIds="#{ {'mail'} }" >*//
// <property name="activationCondition">//
// <!-- docusign multiple c:candidates -->//
// <bean
parent="shibboleth.Conditions.RelyingPartyId"//
//c:candidates="#{{'https://account.docusign.com/organizations/bf2a2a29-SECRET/saml2',
'https://account-d.docusign.com/organizations/bd30f5b2-SECRET/saml2'}}" />//
// -->//
// </property>//
// </bean>//
// </util:list>//
/
[2] /
/
Here in /saml-nameid.xml / I guess I could add another bean based on
/*p:attributeSourceIds="#{ {'eppn'} }" >
*/
and appropriate c:candidates= entityIDs ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210319/d45450cf/attachment.htm>