problems seemingly caused by transientID in O365

[Rob Gorrell]

So you are talking about something like:
 nameIDFormatPrecedence="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
But what if I have two nameid's encoded as persistent (like ImmutableID and
eduPersonTargetedID") and my filter releases them both, which one wins? Or
is that something i must control with the filter, making sure i'm not
releasing two nameid's of same encoded format?

-Rob



On Wed, Aug 27, 2014 at 10:00 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 8/27/14, 9:54 AM, "Rob Gorrell" <rwgorrel at uncg.edu> wrote:
>
> >gotcha, i'm learning something here. so since I'm after releasing a
> >custom nameid to this SP, it would look like:
> >
> >
> >   <rp:RelyingParty id="urn:federation:MicrosoftOnline"
> >provider="https://prdidp.uncg.edu/idp/shibboleth"
> >         defaultSigningCredentialRef="IdPCredential"
> >nameIDFormatPrecedence="ImmutableID">
>
> No. You specify the SAML format you want, has nothing to do with the
> underlying attribute. You need something able to encode to the format you
> choose.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Robert W. Gorrell
Systems Architect, Identity and Access Management
University of NC at Greensboro
336-334-5954
PGP Key ID B36DB0CA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140827/643962a5/attachment.html