What's in this article:
- About member access
- Setting up member access
- Referring URL
- Shared Username and Password via JSTOR
- Proxies
- Google or Microsoft Single Sign-On
- Shibboleth
About Member Access
Publishers can join the Member Access program (formerly called Individual Access Program) to allow society members or journal subscribers to access their journals’ issues on JSTOR.
Setting up Member Access
JSTOR offers the following access options:
Referring URL
If you already have a member log-in area on your own site, JSTOR can enable access so that members log in to the publisher site and then link back to JSTOR, where they will be authenticated to access journal(s). Contact us for assistance in testing or troubleshooting referring URLs.
JSTOR requires the URL from the publisher’s website that contains the link back to JSTOR. The URL must be behind a secure log-in area on the publisher’s site so that it can be accessed only by those with the appropriate login credentials.
In order to enable referring URL access to JSTOR, take the following steps:
- Place this link to JSTOR on a password protected page: https://www.jstor.org
- Send us the URL of the page you placed the link on
- Await confirmation that the link has been approved and added to our authorization system
Please note that the following must be true for a successful referral:
- The referring URL is a password-protected page.
- The referrer does not include embedded code (such as JavaScript)
- The referrer does not include scripting to open in a new tab
- Users do not have security software on their computer that strips the referrer information from the headers.
Shared Username and Password via JSTOR
Shared username and password credentials may be used by many subscribers at the same time. These credentials may also be circulated to all relevant subscribers. No technical set up is required by the publisher, and it will be the responsibility of the publisher to distribute this shared username and password with their members and subscribers.
This access method will not interfere with the use of free personal JSTOR accounts.
Shared Username and Password access is only available for eligible publishers. If we determine that your institution is eligible, we will issue the remote username and password when we set up your access. If you have questions about eligibility, or you would like to update the remote username and password for your publishers, please contact us at service@jstor.org.
Proxies
Proxy servers can be set up via IP address to allow users access to JSTOR. The proxy must require authentication to restrict it to authorized users only. Provide us with your proxy server IP and we will add it to your account. If you are using EZProxy, you may want to review our recommended set-up.
Google or Microsoft Azure Single Sign-On (SSO)
If you are using Google or Microsoft Azure as your single sign-on (SSO) method, we can help you configure it to allow access to JSTOR. Our system will recognize any member logging into Google or Microsoft with your institution's domain name and provide institutional access. Note this domain must be unique to your institution and cannot be shared across multiple institutions within a district.
When logging in through Google or Microsoft SSO you'll be required to create or log into a personal JSTOR account.
To set up SSO access, please contact us and include all of your institution's domains in the request to get started.
Shibboleth
Shibboleth is another Single Sign On method that allows users to authenticate via their institutional credentials to access JSTOR. In order for JSTOR to enable access via Shibboleth, we have to belong to the same federation that you do. Here is a list of federations we currently belong to:
- eduGAIN (Federation Membership Organization) [metadata]
- InCommon (United States) [metadata]
- OpenAthens (Multiple Countries) [metadata]
- DFN-AAI (Germany) [metadata]
Contact us with the following information to begin the setup process:
- The name of the federation to which you belong
- Your Shibboleth Identity Provider ID (entity ID), and
- The list of campuses (if more than one) served by that ID