Attribute definition type for eduPersonTargetedID?

[Wessel, Keith]

Hi, Scott,

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. We can certainly start migrating them to a new attribute, but that's obviously not a trivial process. If the answer to my question is that there's no other way to define eptid with its current value as an attribute in the IdP once the SAML2NameID attribute definition type goes away, we'll start down that road right away. We'd prefer to do this in a more organized fashion, though, along with migrating other identifiers to new formats.

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.

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?

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Monday, July 26, 2021 7:17 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Attribute definition type for eduPersonTargetedID?

What SP claims to "only" support something that virtually no software even supports?

There was a time that SimpleSAML supposedly didn't support persistent NameIDs, something I questioned even at the time. Is that really still the case? And why wouldn't it take a very trivial change to fix that, unless it doesn't support any NameIDs at all...

-- Scott


-- 
For Consortium Member technical support, see https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!DZ3fjg!tpEPZ7vNskiCNRX-6bt1KYTVLWljLKvgwqm8HS3ExoueT4ExkBCTh_J9KC7PI8jMcA$ 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net