computedID in idpv3
Paul B. Henson
henson at cpp.edu
Mon Feb 15 15:40:51 EST 2016
> From: Tom Scavo
> Sent: Monday, February 15, 2016 5:19 AM
>
> That's true in any case so it boils down to the will to do it on your
> part. Let me give two more reasons to try: 1) the saml2int deployment
> spec says so, and 2) the rest of the world follows the saml2int spec
> fairly closely. So if you are exporting your IdP metadata to eduGAIN
> (which I think you are), you have more incentive to take the plunge
Yes, we are. We are releasing eduPersonTargetedID in seven policies. One of them is EDUCAUSE. I know they asked for it at the time, do you know if they are still using it? We are also releasing eduPersonPrincipalName to them. If they have switched to the latter as a unique identifier then perhaps I can stop releasing eduPersonTargetedID and cross them off my migration list. Another is the Research & Scholarship Attribute Bundle:
https://spaces.internet2.edu/display/InCFederation/Research+and+Scholarship+Attribute+Bundle
If it is deprecated, why is it still listed there :)?
For now, I'm just going to keep it, I don't want to deal with the headache of trying to migrate service providers off of it at the same time I'm trying to do a major IDP upgrade. Thanks for the info though, I'll start trying to chip away at it one SP at a time once the upgrade is complete.
Thanks...
--
Paul B. Henson | (909) 979-6361 | http://www.cpp.edu/~henson/
Operating Systems and Network Analyst | henson at cpp.edu
California State Polytechnic University | Pomona CA 91768
More information about the users
mailing list