JSTOR and EZProxy (and Athens authentication as well)

Trusted archives for scholarship
Dear JSTOR Participant,
This message contains information for those JSTOR sites that provide remote access to users either via EZProxy software or Athens authentication. We would very much appreciate it if you could forward this message to the appropriate technical contact at your organization. We apologize for the inconvenience that any of you are experiencing as a result of these issues. For current information about these and other known issues about the new JSTOR platform, you may access our updates page at http://support.jstor.org/update.html.

Sincerely,
JSTOR User Services

EZProxy

After the launch of the new JSTOR platform on April 4, many institutions using EZProxy reported that their users were having difficulties authenticating to JSTOR. Thanks to Chris Zagar, the creator of EZProxy, we now have updated configuration information to share with sites that have been experiencing problems with EZProxy/JSTOR interactions.

EZProxy server settings should be as follows:

  1. The JSTOR database definition should be:
    Option DomainCookieOnly
    Title JSTOR
    URL http://www.jstor.org/
    Domain jstor.org
    Option Cookie
  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 at:
    http://www.oclc.org/us/en/support/documentation/ezproxy/cfg/ssl/

We hope this information helps to resolve related access issues. Please contact support@jstor.org if you find that problems still exist after these configuration changes are in place.
Athens

Since the launch there have also been two major issues identified with Athens access to JSTOR. The first is that the new JSTOR system is not retaining Athens authentication details under certain situations. The second issue is that links from MyAthens pages are not being directed to the right place. The JSTOR technical team is urgently working this afternoon to correct these issues. We are currently testing the fixes and are targeting to apply them within the next 24 hours.

Contact us


© 2008 JSTOR | All Rights Reserved | Privacy Policy | Unsubscribe

Comments are closed.