Tell me more about your single sign-on (SSO) beta

Features

Our SSO allows your staff to sign in using their local credentials instead of their separate LibraryH3lp username and password.

Optionally, the local administrator can fully disable Libraryh3lp username/password authentication, so that SSO authentication is required.

The local administrator can map each user's SSO identifier (local username) to the associated LibraryH3lp username as part of initial setup, or users can associate them at their first SSO login.

Requirements

Any SAML-based single sign-on (SSO) system should work.  This includes Shibboleth and most Active Directory implementations, as long as they support SAML. 

Your Identity Provider (IdP) must release user details to our Service Provider (SP) in a Name Identifier <NameID> element within the SAML <subject> element. 

Your IdP must release an identifier that stays persistent for each user across logins, not one that is transient and will change. 

Limitations

You will still need to create LibraryH3lp users for your staff; LibraryH3lp user creation is not automated through SSO.

We do not at present have any guest-related SSO features. 

Note: if guests are already authenticated on your web site, AND you have an entry form on the chat box, then a hidden entry form field on the chat box can receive the guest’s identity dynamically as a URL parameter.

Next-steps

If you'd like to try it out, please contact us at support@libraryh3lp.com.  We'll need a metadata URL for your IdP.  Thanks!

FAQ URL: