Hi Eric,

I see that your institution is a member of InCommon. It is likely that your IdM group will have implemented a default attribute release policy that is based around InCommon conventions. JSTOR is also a member of InCommon, so there should be some common expectations.

Use of Shibboleth has really expanded over the last N years. On our campus is now used heavily for all sorts of applications outside of the library: administrative systems, granting agencies, etc., lots of internal and external SPs. A far cry from the early-adoption days.

I suggest talking to your IdM group how this transition might work, what concerns you might have, and whether they would share those concerns.

-Tod

Tod Olson <[log in to unmask]<mailto:[log in to unmask]>>
Systems Librarian
Interim Head of Integrated Library Systems
University of Chicago Library

On Mar 25, 2021, at 10:50 AM, Hammer, Erich F <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Hi.

We are just starting to investigate moving access some of our larger eResource vendors away from going through EZProxy and onto SSO/Shibboleth.  Our test case is JSTOR, and our Identity Management group that supports Shibboleth is asking about other libraries using the eduPersonEntitlement attribute.  We are specifically NOT interested in OpenAthens.

I'm also interested to know if anyone has a handle on a "standard" Shib attribute used by most/many of the larger vendors, or if this is going to be a rabbit hole where every vendor wants a different attribute and repeatedly negotiating with the IDM group for changes will put us on the "bad list".

I'm open to other comments and criticisms about the whole idea too.

Thanks,
Erich


--
Erich Hammer            Head of Library Systems
[log in to unmask]<mailto:[log in to unmask]>         University Libraries
518-442-3891              University @ Albany

Power corrupts; Absolute power corrupts absolutely;
God is all-powerful. Draw your own conclusions.