Managing My Collection
Accessing Usage Statistics
To set up IP authentication for your institution, you will need to provide JSTOR Support with a list of the IP addresses that your institution uses to access electronic resources.
Please note that addresses of the type 10.*.*.* and 192.168.*.* are reserved for use in internal networks, such as computers that are behind a firewall or a proxy server. In order for our servers to recognize users at such addresses, we would need to add your external IP addresses to our records, which we will be happy to do, provided that these are static addresses and not shared with any other organizations.
Whenever your institution makes any changes to the IP addresses it uses to access JSTOR, you can submit these updates to JSTOR Support
All participating institutions have the option of setting up remote access to JSTOR for their users along with onsite access. The main methods of remote access that we support are proxies
, federated options like Athens
, and shared activation links
. We do offer several other remote access options when the main supported methods will not work for your institution. Please contact JSTOR Support
for assistance selecting and setting up the best remote access method for you.
You are welcome to allow users to access JSTOR via a proxy server, so long as access to the proxy server is restricted to authorized users at your institution. Read more about proxy servers
, and our policies regarding them.
On our end, the only configuration necessary would be to ensure that the IP address for your proxy is enabled to access JSTOR. In order to enable a proxy server for your institution, please submit this IP address to JSTOR Support
In order to enable your JSTOR access via EZProxy, all we typically need from you is the IP address of your EZProxy server. Feel free to send it to JSTOR Support and we will make the necessary changes.
OCLC's support team should be able to help you with your EZProxy set-up, however the configuration we typically recommend for JSTOR access is as follows:
1. The JSTOR database definition should be:
2. In addition, EZProxy must be explicitly configured to handle https. If https handling is not already set up, users will lose proxying when they arrive at the JSTOR login page, and the connection will be lost. If this is the case, SSL configuration must be performed using the information provided by OCLC
Athens is a federated login service used by many institutions developed by Eduserv, which you may read more about on the Eduserv website
. JSTOR partners with Athens-enabled institutions to allow users to access JSTOR by signing in through their institution from the JSTOR website. In order for an institution or organization to access JSTOR through Athens, the JSTOR resource must be allocated to the institution. To enable Athens access, please contact JSTOR Support
requesting Athens as your access method.
JSTOR Support will then request that Athens allocate the JSTOR resource to your institution. Once Athens has done so, it will notify your Athens site representative, who must then grant access to the JSTOR resource for your users.
Shibboleth is open source software that provides institutions with Single SignOn, a system of authentication procedures, protocols, and technologies that enable end users to access multiple online resources with one set of credentials. The Shibboleth system allows organizations to exchange information about users securely and privately. More detailed information may be found on the Shibboleth website
JSTOR partners with Shibboleth-enabled institutions to allow users to access JSTOR by signing in through their institution from the JSTOR website. However, in order for an institution or organization to access JSTOR through Shibboleth, JSTOR and the organization must be a member of the same federation. A list of federations may be found on the Shibboleth Federations website
If you would like to enable access to JSTOR through your institutional log in, please contact JSTOR Support
with following information:
+ Which federation (or federations) your institution is a member of
+ Your institution's Shibboleth Identity Provider ID
+ The list of campuses (if more than one) the Identity Provider serves
Once this information is in our records, your Attribute Authority can authorize users into JSTOR by asserting the eduperson entitlement attribute with a value of urn:mace:dir:entitlement:common-lib-terms.
A shared activation link is ideal for small institutions and those with limited technical infrastructure or IT resources. Shared activation links will enable individual users to access JSTOR and register for a MyJSTOR account. Once a user has followed the activation link and registered for a MyJSTOR account, she will be able to use the username and password of his choice to access JSTOR in the future. You would be free to disseminate the provided link to authorized users at your institution with the understanding that it would be for their exclusive use. If you maintain a password protected site, this would be an acceptable location to publicize the JSTOR Shared Access Token information. However, please note that the token URL must not be posted on public web pages, where it might become available to unauthorized users.
JSTOR’s Institution Finder
assists unauthenticated users at your institution to access full-text content on JSTOR. Here's how it works:
1. A user arrives on a JSTOR article page from a Google search or other referring page
2. An on-campus user will get automatic access to the full-text, but users outside of the institution’s IP range will be denied access
3. When denied access to the full-text, the user is presented with options for accessing JSTOR, including a link to the JSTOR login page and the Institution Finder
4. From there she can search for their institution and follow a link to your proxy login page
5. After logging in, she is authenticated to JSTOR and will be automatically redirected to the original full-text article
If you are interested in this functionality for your library, we need only to confirm your EZProxy prefix, which should look something like this:
JSTOR is part of the ITHAKA family