Attribute definition type for eduPersonTargetedID?

[Spencer Thomas]

As the tech admin for an SP that can accept ePTID, I am just a little bit confused. We do not require either name format in our SP metadata, but one of our applications wants a “name ID” value.  This is what our support document says:
Attribute Name
Description
Example
urn:oid:1.3.6.1.4.1.5923.1.1.1.10 or urn:oasis:names:tc:SAML:2.0:nameid-format:persistent (persistent-id) REQUIRED
Persistent identifier that provides Artstor (SP) with a unique identifier for the account holder
URL of IdP!SP Entity ID! Unique Identifier

I see that the first one is eduPersonTargetedID). The second one appears to be specifying that we will accept NameID in that format (which could be written a little more clearly, I think).
Our attribute-map.xml has these entries that map both to the same “friendly” name for further processing:
<Attribute name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" id="persistent-id">
   <AttributeDecoder xsi:type="NameIDAttributeDecoder" formatter="$NameQualifier!$SPNameQualifier!$Name" defaultQualifiers="true"/>
</Attribute>

<Attribute name="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" id="persistent-id">
    <AttributeDecoder xsi:type="NameIDAttributeDecoder" formatter="$NameQualifier!$SPNameQualifier!$Name" defaultQualifiers="true"/>
</Attribute>

>From this conversation, I think we should stop listing ePTID in our support documentation, although we should continue to recognize it.
>From Scott’s comments, it would seem that we don’t need to make any changes to our metadata.

--
Spencer Thomas
Technical Architect / JSTOR and Artstor
ITHAKA<https://www.ithaka.org/> / 301 E. Liberty St, Suite 250, Ann Arbor, MI 48104
Email: Spencer.Thomas at ithaka.org<mailto:Spencer.Thomas at ithaka.org>
Voicemail: +1-734-887-7004


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210726/8f92fe6c/attachment.htm>