1 / 12

Accelerating Access Change at JSTOR: Shibboleth Implementation

Learn how JSTOR, a scholarly resource organization, utilized Shibboleth for access, motivations for change, and ideas for faster implementation. Explore the benefits of transitioning from IP addresses to Shibboleth and the importance of standardization.

heidir
Download Presentation

Accelerating Access Change at JSTOR: Shibboleth Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JSTOR as a Shibboleth Target David Yakimischak davidyak@jstor.org

  2. Agenda • JSTOR Overview • Auth/Auth Past • IP Addresses • JSTOR needed a solution • Motivation to change • Some ideas to accelerate change • Discussion

  3. JSTOR Mission • JSTOR is a not-for-profit organization with a mission to help the scholarly community take advantage of the advances in information technology. This includes: (1) building a reliable and comprehensive archive of core scholarly journals, and (2) dramatically improve access to this scholarly material • In pursuing its mission, JSTOR takes a system-wide perspective, seeking benefits for libraries, publishers and scholars

  4. JSTOR Today • Over 2,000 participating libraries • Over 200 participating publishers • Over 400 journals online • 15 million pages scanned (and counting!) • Access is at least 10x greater than paper • (full-text searching is a benefit, along with access from outside of the physical library)

  5. JSTOR Monthly Usage Meaningful Accesses

  6. Auth/Auth Past

  7. 90%+ of Auth is IP Addresses • It identifies the machine, not the user • Problems when user is off-campus (proxies) • Problems with NAT, DHCP, firewalls • Proxies (especially open) are a problem • But it is simple and it works • Each resource maintains its own database

  8. JSTOR needed a solution • Shibboleth appeared to have the right characteristics • Implementation was easy; it worked • Fortunately we had previously separated authentication and authorization • Pilots work very well

  9. Attributes • Currently we accept the eduPersonAffiliation attribute and map that to what we call a ‘site’ • Some problems with mapping when one eduPersonAffiliation maps to more then one JSTOR site • Have not yet experimented with entitlements • Federations are helpful but we don’t need a lot of them

  10. Motivation to change • It’s either got to be better or cheaper (or both) • Ability to enforce current licensing agreements and support new models • Cost-effectiveness from this and • Lower cost of support (e.g. IP databases) • Universal standardization

  11. Some ideas to accelerate change • A resource provider might issue a challenge to the community to stop using IP address authentication • Lower access fees? How about a charge for using IP addresses, or a charge to make changes? • Point solutions: portals, metasearching, remote access • Username/passwords can become a Shibboleth origin at JSTOR • Same for IP address authentication • Central IP address registry as a migration mechanism to Shibboleth

  12. Discussion

More Related