Storing persistentId using an HTTP DataConnector at at
Tue Nov 8 16:54:11 UTC 2022

Thank you and Nate.   In fact, I am just a bit dumb and/or blind : I have read these pages a couple of times, edited my saml-nameid.* files even more. But if I am not able to spot "#idp.nameid.saml2.default = urn:oasis:names:tc:SAML:2.0:nameid-format:transient", what to do ?   So with "idp.nameid.saml2.default = urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" I get the expected result ! 
Regards     Le 08-Nov-2022 16:56:13 +0100, users at a crit: 
* spf via users  [2022-11-08 16:30]:
> The only thing I can't undersand for now is how to have a persistent
> NameID in the SAML assertions. If the SAML2PersistentGenerator only
> is enabled, there is even no subject. But if SAML2TransientGenerator
> or both are enabled, I have a 

In my conf/saml-nameid.xml within  I have multiple *Generator
elements, all "active" in the configuration and used when needed
(based on the NameID selection process Nate pointed you to):
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list