Remote Access

From LexisNexis Academic Knowledge Center
(Difference between revisions)
Jump to: navigation, search
(LexisNexis RPA Script)
 
 
Line 28: Line 28:
 
[[Category: FAQ]]
 
[[Category: FAQ]]
 
[[Category: For Electronic Resources Administrators]]
 
[[Category: For Electronic Resources Administrators]]
 +
[[Category: Tech Support]]
 +
[[Category: Interface Refresh]]

Latest revision as of 11:38, 6 December 2013

Institutions that have have a secure patron authentication system are allowed to provide remote access to their LexisNexis subscriptions as set out in the LexisNexis Subscriber Agreement. LexisNexis supports remote access using the methods listed below.

Contents

Supported Remote Access Methods

Proxy Server

This is the preferred method for remote patron authentication. If you allow only properly authenticated users to log in to your secure proxy server, LexisNexis can add its IP address to your subscription. Proxy servers may require special configuration to work with LexisNexis resources. Please see the guidelines below for specific proxy servers that have been tested with LexisNexis Academic.

EZProxy from OCLC

Note: LexisNexis Academic requires EZproxy 5.0 or later. Please see OCLC's official EZProxy Configuration Instructions for LexisNexis

Please note that the recommended configuration should be followed exactly. If your EZProxy connection is not working properly, the first thing to check is whether your configuration matches the OCLC recommendation exactly. Customer support is provided by both OCLC and LexisNexis.

Innovative Interfaces WAM Proxy

Subscribing institutions have reported success in using the WAM proxy to control user authentication for LexisNexis Academic. Please contact Innovative Interfaces for configuration directions.

LexisNexis RPA Script

Libraries that do not use a proxy server or VPN, but have a secure portal for authorized users may want to use the Remote Patron Authentication (RPA) script developed by LexisNexis. To use the script, libraries must be able to install it on their institution's server and they must sign a short addendum to their license agreement.

Remote Access Methods Not Supported

The following authentication methods are not supported because they do not provide adequate security to protect the intellectual property of LexisNexis and its content partners.

Referring URL

Referring URL is easily spoofed, so it is not acceptable as an authentication method.

Shared ID/Password

LexisNexis recognizes that libraries have little or no control over the actions of their patrons. Therefore, LexisNexis will not issue an ID to be shared with patrons. We have seen multiple instances of such IDs being posted on the Internet or shared with unauthorized users.