> I don't understand the technical details involved.
If you want to, the technical details are discussed here:
https://spaces.internet2.edu/display/SHIB2/NativeSPTargetedID
Also the Technical Recommendations For Participants (TRFP) Section 7.1.3
Basically:
- it used to be [mumble]@scope.ac.uk. This has been deprecated by Shib
Devs for some time but for historic reasons it still something which the
TRFP suggests that you generate.
- The recommended format is <Idp>|<Sp>|[mumble]. You are also encouraged to
generate that.
Andy's results are exactly what I would expect from correctly set up Shib2
IdP. The important thing is the UlNWiIQjIQsnLzQVoL7YIyK8mBU bit. This is
what you should see from both IdPs.
As an aside, if you are using the StoredIdConnector there was a bug which
meant that this that value was not carried forward. This is fixed since (at
least) 2.1.4.
Rod
----- Original Message -----
From: "Adrian Barker" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, December 02, 2009 9:52 AM
Subject: The eduPersonTargetedID and Shibboleth 2
> We are planning to migrate to Shibboleth 2, and need to verify that the
> eduPersonTargetedID will not change, but I'm not sure how to test this. We
> are running a Shibboleth 1.3 IdP and 2.0 IdP in parallel, with the same
> entityID, and can point a test Service Provider at one or the other IdP
> and display the attributes, but the format of the eduPersonTargetedID has
> changed, and I don't understand the technical details involved.
>
>
>
> Thanks for any help.
>
>
>
> Adrian Barker.
>
>
> --
>
> Adrian Barker,
> Internet Technology Section
> Information Systems
> University College London, Gower Street, London WC1E 6BT
> External phone: +44 20 7679 5140, Fax (+44) 20 7388 5406
> Internal phone: x 25140
> Email: [log in to unmask]
|