eduPersonTargetedId differs between Shibboleth IdP v2 and v3

[ROGERS Richard M]

Hi,

I'm currently going through a migration from Shibboleth IdP v2 to v3. It all seems to be going OK except that the released values of eduPersonTargetedId are different between the two. I've checked the configurations and can see no difference:

    <!-- EpTid (new) -->

    <resolver:AttributeDefinition id="eduPersonTargetedID" xsi:type="SAML2NameID" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
        nameIdFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
        sourceAttributeID="computedID">
        <resolver:Dependency ref="computedID" />

        <resolver:AttributeEncoder xsi:type="SAML1XMLObject" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
                name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" />

        <resolver:AttributeEncoder xsi:type="SAML2XMLObject" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
                name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" friendlyName="eduPersonTargetedID" />
    </resolver:AttributeDefinition>

...

    <!-- Computed targeted ID connector -->

    <resolver:DataConnector xsi:type="ComputedId" xmlns="urn:mace:shibboleth:2.0:resolver:dc"
                            id="computedID"
                            generatedAttributeID="computedID"
                            sourceAttributeID="objectSid"
                            salt="{same in each case}">
        <resolver:Dependency ref="myLDAP" />
    </resolver:DataConnector>

Both implementations are on Windows; v2 uses Tomcat, v3 uses Jetty (with more recent Java). Anything else that could make a difference? (32-bit vs. 64?).

Thanks for any suggestions.

Regards

Richard
--
Richard Rogers
Principal IT Officer, Client Technology and Applications
Information Services, Staffordshire University
Tel: 01785-353785

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160821/5b078c7f/attachment.html>