IdPv3 - eduPersonTargetedID - How to define and release this attribute?

Waldbieser, Carl waldbiec at lafayette.edu
Thu Mar 17 12:14:33 EDT 2016


Scott,

I am totally open to releasing EPTID as a NameID.  I'm just not sure what (if anything) I need to do at a technical level to make that happen.
The instructions for setting up a Name ID generator are pretty clear.  But I am not sure where I go from there.  I am thinking that I need to configure *something* to make the Name ID available to an R&S supporting SP-- but I don't know what that *something* is.

Thanks,
Carl

----- Original Message -----
From: "Cantor, Scott" <cantor.2 at osu.edu>
To: "Shib Users" <users at shibboleth.net>
Sent: Thursday, March 17, 2016 11:54:08 AM
Subject: RE: IdPv3 - eduPersonTargetedID - How to define and release this attribute?

> What I am really interested in is configuring IdPv3 to support the global R&S
> category.
> The information I have read[1][2] suggests that eduPersonTargetedID is
> recommended and possibly required to be released to support this category
> if ePPN doesn't fit certain criteria.

You probably should read this [1] if you don't know the backstory of ePTID. It is written from an SP perspective and covers a somewhat separate set of issues, but it discussed the interplay involved here. The thing you're asking about is the thing in the section labeled "SAML 2.0 Attribute" and the thing I'm talking about is before it in the section called "SAML 2.0 NameID".

I don't believe that you need to support eduPersonTargetedID in attribute form to support R&S, using a persistent NameID should be fine. I also suspect that isn't clear from R&S itself.

-- Scott

[1] https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPTargetedID

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list