Attribute definition type for eduPersonTargetedID?
Cantor, Scott
cantor.2 at osu.edu
Mon Jul 26 14:12:56 UTC 2021
On 7/26/21, 10:04 AM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:
> I didn't actually say they only support eptid. I said they need it, and I say need because it's what they're
> currently using as a unique identifier.
Persistent ID is the *same* identifier. This is not about identifier migration, which is hard, it's just about syntax.
> We can certainly start migrating them to a new attribute, but that's obviously not a trivial process
If the value is the same, it should be very trivial.
> But since eptid is part of the R&S bundle, the impacts of this could be more far reaching than just local SPs
> that use it as a unique identifier, and simply replacing it with something else is likely to break a lot.
R&S also assumes use of the persistent NameID Format, because that's in fact what eduPersonTargetedID *is* in any recent version of the eduPerson spec.
> I'm all for migrating to the new identifier attributes as soon as we can, but I know that's going to take some
> time, and I'd like to continue supporting it with an attribute definition that doesn't use a deprecated type. Is
> there a way?
No.
-- Scott
More information about the users
mailing list