RPAS vs EZproxy

Determining which link to use

You should continue to use any existing RPAS links which you have in place. RPAS provides a more direct (faster through the Internet) route for searching a database. EZproxy links should be used when you want to provide remote access for patrons to databases that are IP accessible only and when you want to create direct links to the journal, article, or title level. If you have any questions about the best way to configure individual databases, please email us.

Remote Authentication (RPAS)

RPAS links begin with https://rpas.klnpa.org/remote/validate.cgi

RPAS links generally provide access to a database search page. They can be configured when vendors can provide one of the following access methods:

  1. Username/Password on a web-based form
  2. Referring URL
  3. Server-side script

Database Website Access through RPAS Links

  • On-campus patrons: Direct — After IP authentication, the on-campus patron’s access to the vendor’s database is direct.
  • Remote patrons: Direct — After initial authentication, the remote patron’s access to the vendor’s website is direct.

EZproxy

EZproxy links begin with http://navigator-xxx.passhe.edu/login?url=

EZproxy links are required for these two instances:

  1. To authenticate databases that are IP-accessible only.
  2. To create direct links down to the journal, title, or article level within a particular database such as EBSCO.

Database Website Access through EZproxy Links

  • On-campus patrons: Direct — After IP authentication, the on-campus patron’s access to the vendor’s database is direct.
  • Remote patrons: Proxied — All interaction between the remote patron and the vendor’s website is passed through the EZproxy server in Shippensburg.