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 customizations customization settings to enable this authentication, it does require technical knowledge of setting up your external institutions authentication system and having that server send information to the ILLiad web serverto implement.
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 that is to be set to by the authenticating system and passed to ILLiad via the an HTTP header.
ILLiad installations have successfully authenticated users via PubCookie, CoSign, CAS, and Shibboleth using this type of authentication.