Attribute definition type for eduPersonTargetedID?
Cantor, Scott
cantor.2 at osu.edu
Mon Jul 26 15:46:10 UTC 2021
On 7/26/21, 11:40 AM, "users on behalf of Peter Schober" <users-bounces at shibboleth.net on behalf of peter.schober at univie.ac.at> wrote:
> Well, given the case-folding issue I'd not recommend to carry forward
> the existing (case-sensitive, base64-encoded) persistent NameID values
> as pairwise-id values and instead move to (case-insensitive,
> base32-encoded) different pairwise-id attribute values instead.
I wasn't referring to the virtual impossibility of rekeying systems. I know exactly how impossible that is. I was strictly talking about the IdP code we're talking about here, not the overall deprecation of the "abstract" attribute.
When the time comes, I don't know that we're going to pull the code. It's hard to envision doing so right now. What I do know is, we're not documenting it and not supporting it, which isn't a change, and we will keep the warning because we're not promising not to yank it if something unexpected happened.
-- Scott
More information about the users
mailing list