transient vs persistent custom nameids
Cantor, Scott
cantor.2 at osu.edu
Wed Jan 27 14:07:12 EST 2016
On 1/27/16, 2:00 PM, "users on behalf of brabec at ncsu.edu" <users-bounces at shibboleth.net on behalf of brabec at ncsu.edu> wrote:
>We have a 3rd Party SP doing some kind of SAML2. They expect us to
>return the SAML NameID as urn:oasis:names:tc:SAML:2.0:nameid-
>format:transient with the value = our numeric campus id. This has been
>setup and working for us in V2 for a while now.
That isn't a proper use of that format.
>I can also change the same block to
> p:format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
Also, though less, wrong to do that.
>Is there a bean / attribute I can add to the above to tell the generator
>to treat this is a persistent, but label it transient without using the
>transient generator in its place?
You would have to take out the built in transient generation beans, or attach an activation condition to them that tells them not to run if the SP matches the broken one.
I certainly not recommmend anything like that. You're making your life painful to accomodate a broken peer.
-- Scott
More information about the users
mailing list