fluidreview?

Liam Hoekenga liamr at umich.edu
Tue Oct 20 13:13:53 EDT 2015


On Tue, Oct 20, 2015 at 10:28 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> That's not any form of ePTID that ever existed.
>

A combination of them updating our metadata and us using the right
definition for ePTID seems to have done it:
    <resolver:AttributeDefinition xsi:type="ad:SAML2NameID"
id="eduPersonTargetedID"

nameIdFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
sourceAttributeID="computedID">
        <resolver:Dependency ref="StoredIDConnector" />
        <resolver:AttributeEncoder xsi:type="enc:SAML1XMLObject"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2XMLObject"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" friendlyName="eduPersonTargetedID"
/>
    </resolver:AttributeDefinition>

Our signing key didn't change with the upgrade.. not sure why it didn't
work w/o the metadata update.

Any suggestions on getting vendors who want to use the attribute version of
ePTID to move away from it (since the IdPv3 support for ePTID is
deprecated)?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151020/14521693/attachment.html>


More information about the users mailing list