Why do some ILLiad users lack user information from SAML (stub accounts)?
Applies to
- ILLiad libraries using RemoteAuth
Answer
When an ILLiad library is using RemoteAuth or SAML, the patron load from the UserValidation table holds the pre-loaded information for each user. When the user authenticates with their SSO on the ILLiad website for the first time, their UserValididation information is loaded onto the NewAuthRegistration form. When the user submits that form, it creates an account in the database using that information.
If a patron clicks on an OpenURL link from an online public access catalog (e.g. Primo, FOLIO, etc), and they are already logged into their SSO, ILLiad will still create the account, but it bypasses the NewAuthRegistration page that normally loads the users information. Then, if the patron requests the item, it will be associated with an account, but their account would be a stub, missing almost all relevant information besides am email address or username.
The best fix for these cases is to have the user log onto the library's main ILLiad page and complete the registration form. If you have stub users that are not associated with any requests, you are able to delete them using the Database Manager.
Additional information
Here is the Atlas UserVoice page for requesting this feature: https://uservoice.atlas-sys.com/foru...unts-to-comple
Here is more information on RemoteAuth: https://support.atlas-sys.com/hc/en-...cation-Process