Hi Jiri,
Thanks for your question.
We are not going to change our metadata in the federations.
Elsevier SP requires an entitlements attribute through some federations but not all. The reason we don't require it through all federations, yet, is our historical implementation and the fact if we start requiring it from all IdPs, those that aren't able to release it would lose access. We would like to require it as a rule but that is currently just not possible. Adding an entitlement attribute as a requirement to our metadata when we aren't able to honor it would be misleading.
Elsevier SP recommends the release of ePTID or a Persistent NameID that is being used for personalization. We recommend its release but we don't require it.
We don't need any other user attributes and those are that being sent to us are just being ignored.
Kind regards, Meshna
Meshna Koren
Associate Product Manager Product Management - Identity and Platform - Research Products
Elsevier BV Radarweg 29, Amsterdam 1043 NX, The Netherlands m.koren@elsevier.com
-----Original Message----- From: FIM4L fim4l-bounces@lists.daasi.de On Behalf Of Jiri Pavlik Sent: Tuesday, September 17, 2019 13:58 To: fim4l@lists.daasi.de Subject: Re: [Fim4l] Elsevier Federated Authentication changes (was RE: Hello and brief intro)
*** External email: use caution ***
Hi,
thanks a lot for sharing the info at FIM4L list, Chris. I like the planned changes as Jos does.
Are you going to add required attributes at Elsevier SP metadata in eduGAIN [1] similary to the SP metadata in eduID.at[2] or SWITCHAii/SWITCH edu-ID? Actually I believe Elsevier is using name and e-mail address if provided by IdP so displayName, mail, givenName, sn can be among optional attributes in the SP metadata.
Best regards
Jiri
1. https://met.refeds.org/met/entity/https%253A%252F%252Fsdauth.sciencedirect.c... 2. https://met.refeds.org/met/entity/https%253A%252F%252Fsdauth.sciencedirect.c...
On Fri, Sep 13, 2019 at 8:14 AM Jos Westerbeke jos.westerbeke@eur.nl wrote:
On 12/09/2019, 22:28, "FIM4L on behalf of Shillum, Chris (ELS-NYC)" <fim4l-bounces@lists.daasi.de on behalf of c.shillum@elsevier.com> wrote:
... We are planning to make the following changes over the new few weeks: ... • Give the users the option to skip the step of creating an Elsevier account if that’s not what they intended to do
+1
cheers, Jos
FIM4L mailing list FIM4L@lists.daasi.de http://lists.daasi.de/listinfo/fim4l
_______________________________________________ FIM4L mailing list FIM4L@lists.daasi.de http://lists.daasi.de/listinfo/fim4l
________________________________
Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.