On Tue, Jul 23, 2019 at 3:57 PM Peter Schober peter.schober@univie.ac.at wrote:
- Peter Schober peter.schober@univie.ac.at [2019-07-23 15:28]:
- Jiri Pavlik jiri.pavlik@mzk.cz [2019-07-23 15:03]:
At eduID.at all IdPs are fine with releasing eduPersonTargetedID according to
<md:EntityDescriptor... entityID="https://sdauth.sciencedirect.com/%22%3E ... I suppose. Is it correct, Peter?
Not sure what this is supposed to demonstrate but anyway:
Naturally -- being neither the IDP that sends data nor the SP who recieves data -- I have no way of knowing this for all euID.at IDPs.
I can add that for any IDP I *know* supports persistent NameIDs in principle -- which is still different from releasing it to anyone in particular -- I do record that in their metadata (NameIDFormat elements with "persistent" as value).
From a quick look that's a bit more than a third of our IDPs (19 out of 55 production IDPs), which still is higher than the current count in eduGAIN (720 out of 3062, so less than a fourth of the IDPs).
But there may be some supporting proper persistent NameIDs without us knowing about it. And there's no record of support for eduPersonTargetedID specifically.
I can see a way ahead here:
- Encourage IdPs to release persistent NameID for Elsevier SP. - Request persistent NameID in Elsevier SP metadata and comply with CoCo. - Offer personalisation at Elsevier services when persistent NameID is released. - Roll out pairwise-id support eduGAIN wide.
Could you agree with that?
Thanks a lot, Peter.
Cheers
Jiri