If you do not want your users to create a username and/or password to use ILLiad, but want them to use and existing institutional username and password to access ILLiad for registration and login, you can setup RemoteAuth authentication. While there are only a few ILLiad customization settings to enable this authentication, it does require technical knowledge of your institutions authentication system to implement.

ISAPI Filters

Icon

Note that RemoteAuth authentication is dependent on your existing external authentication system.  In order to use RemoteAuth authentication with ILLiad, you must implement a means to protect the ILLiad web folder and send an authenticated username, usually with an ISAPI filter. Because the development and support of those ISAPI filters or other configurations for authenticating systems are outside of ILLiad, you will need to be familiar with how to create and support those yourself to use this type of authentication. While Atlas Systems and OCLC can help you troubleshoot the ILLiad portion of the authentication, we cannot diagnose issues related to the authenticating system.

 

RemoteAuth authentication is slightly different than other authentication methods in that there is no login page used for customers to enter a username and password. In most installations, sites add an ISAPI filter to the ILLiad web server that intercepts the request for the illiad.dll in the RemoteAuth folder. If the username value has not been set, it redirects the user to the authentication server. If the username has been set, it checks the authentication server to see if the session is still active. RemoteAuth authentication expects a server variable to be set by the authenticating system and passed to ILLiad via an HTTP header.

  • Currently, ILLiad only checks for the username and does not look for other customer information (i.e. name, status, contact information etc.).
  • The system is designed to use RemoteAuthentication based on the location of the actual web pages as specified by the RemoteAuthWebPath customization key. Therefore, you cannot use the testweb pages with RemoteAuth.

Examples

ILLiad installations have successfully authenticated users via PubCookie, CoSign, CAS, and Shibboleth using this type of authentication.

OCLC Hosted Customers

Icon

If your ILLiad service is hosted by OCLC and you would like to use Remote Authentication, you will need to use their middleware product, EZProxy, to connect your Authentication Service to the ILLiad server.

Remote Authentication Workflow