subject-id and pairwise-id internal ids
Peter Schober
peter.schober at univie.ac.at
Wed Jun 27 09:56:27 EDT 2018
Hey,
I'm writing up a bit of local documentation on on how to support the
upcoming Subject Identifier Attributes
https://wiki.oasis-open.org/security/SAMLSubjectIDAttr
(We have cases where we'd rather start using those now, the
alternative being to ask our member IDPs to add support for
essentially deprecated persistent NameIDs wrapped in essentially
deprecated eduPersonTargetedId attributes -- something I can't get
myself to do in 2018ce.)
So I'd would like to write that documentation it in a way that once
these attributes may be added to the examples shipped with the new IDP
releases that their internal attribute id will match what I've
documented, so that attribute filters would continue to work, etc.
So any idea or preference how you'd call these in the config?
I note 3.3.3 has "eduPersonUniqueId" in its example
attribute-resolver-full.xml, and
intercept/consent-intercept-config.xml references an (otherwise
unused, AFAICT) "persistentId" attribute.
So following these two examples I'm assuming
"subjectId" and "pairwiseId" would be the most likely internal
attribute id for those two new standard attributes?
Cheers,
-peter
More information about the dev
mailing list