Hi Bernd,
I see,
eduPersonScopedAffiliation (required)
eduPersonEntitlement (required)
is working for Freiburg University and
eduPersonScopedAffiliation (required)
eduPersonEntitlement (required)
eduPersonTargetedID (required)
is not.
The university students and staff are free to use personalisation at Lexis
Nexis,
Elsevier, EBSCO, ProQuest services if they want to so
eduPersonScopedAffiliation (required)
eduPersonEntitlement (required)
eduPersonTargetedID (optional)
is working for the University as well.
Is it correct?
All the best
Jiri
>
>> On Sat, Mar 13, 2021 at 2:40 PM Bernd Oberknapp <bo(a)ub.uni-freiburg.de>
>> wrote:
>>
>>> Hi Jiri,
>>>
>>> On 13.03.21 09:15, Jiri Pavlik wrote:
>>>
>>> > When checking ProQuest SP for ProQuest Central in DFN-AAI metadata [1]
>>> > I can see both eduPersonEntitlement and eduPersonTargetedID as
>>> required
>>> > attributes.
>>>
>>> I assume you mean the SP
>>> https://shibboleth-sp.prod.proquest.com/shibboleth? That's obviously
>>> wrong, both eduPersonScopedAffiliation and eduPersonEntitlement are
>>> supported for authorization, but as far as I can tell you don't have to
>>> use them, and eduPersonTargetedID isn't required.
>>>
>>> > Is it safe to assume that if there is personalisation capability at a
>>> > library service then all German universities, libraries are fine with
>>> > releasing eduPersonTargetedID for recognising returning users and
>>> > eduPersonEntitlement, eduPersonScopedAffiliation for authorisation?
>>>
>>> No. I can't speak for other IdPs, but in my opinion that approach would
>>> be wrong, users by default should be able to use services anonymously,
>>> without being recognized as a returning user. Based on what I can see in
>>> the admin tools, only a very small percentage of our users actually uses
>>> the personalization features, so releasing eduPersonTargetedID by
>>> default just for personalization isn't an option. If publishers would
>>> force us to send an eduPersonTargetedID just for personalization I would
>>> consider dropping Shibboleth for those publishers and using our EZproxy
>>> instead.
>>>
>>> Best regards,
>>> Bernd
>>>
>>> --
>>> Bernd Oberknapp
>>> Gesamtleitung ReDI
>>>
>>> Albert-Ludwigs-Universität Freiburg
>>> Universitätsbibliothek
>>> Platz der Universität 2 | Postfach 1629
>>> D-79098 Freiburg | D-79016 Freiburg
>>>
>>> Telefon: +49 761 203-3852
>>> Telefax: +49 761 203-3987
>>> E-Mail: bo(a)ub.uni-freiburg.de
>>> Internet: www.ub.uni-freiburg.de
>>>
>>>
Deal all,
in eduGAIN LexisNexis Advance SP request optionally
eduPersonScopedAffiliation and eduPersonTargetedID attributes. [1] In
Austrian eduID.at it requests these two attributes as required. [2] In
French RENATER it requires eduPersonScopedAffiliation, eduPersonTargetedID,
givenName, sn, mail attributes and supports Code of Conduct and Sirtfy
entity categories. [3]
I am wondering whether everyone could be fine with following set of
attributes along with CoCo and Sirtfy entity categories support:
eduPersonScopedAffiliation (required)
eduPersonTargetedID (optional)
givenName (optional)
sn (optional)
mail (optional)
Universities/libraries may choose to release
just eduPersonScopedAffiliation and be FIM4L privacy stars. It will
correspond to the upcoming REFEDS Anonymous Authorisation entity category.
[4]
Universities/libraries may also choose to
release eduPersonScopedAffiliation and eduPersonTargetedID for enabling
personalisation capabilities. It will correspond to the upcoming REFEDS
Pseudonymous Authorisation entity category. [5]
And finally universities/libraries may also choose to
release eduPersonScopedAffiliation, eduPersonTargetedID and let users
decide about releasing name and e-mail address. [6]
Do you like this kind of approach?
Take care
Jiri Pavlik, techlib.cz
1.
https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com…
2.
https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com…
3.
https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com…
4.
https://wiki.refeds.org/display/CON/Entity+Category+Consultation+Anonymous+…
5.
https://wiki.refeds.org/display/CON/Entity+Category+Consultation+Pseudonymo…
6. https://www.youtube.com/watch?v=znpjHR6LOxs
Dear all,
ever wanted to have statistics reports for e-resources by university
faculties, campuses, departments? Then you may like to check REFEDS
consultation
regarding new attribute proposed to be added to the eduPerson schema:
https://wiki.refeds.org/display/CON/Consultation%3A+eduPersonAnalyticsID
Credits to Heather Flanagan for the consultation info at SeamlessAccess
March 2021 Newsletter.
Kind regards
Jiri
