Technical

Options for Single Sign-On (SSO)

Follow

sso-1.webp

Single Sign-On improves security and makes the logging-in process simpler for staff users. For example, if a user is already logged into their existing identity provider, then accessing Asset Bank could be as easy as clicking a link from their intranet.

It also removes the need to create new user accounts manually, as new staff members in parts of your organisation can automatically be mapped to the relevant permission group. As a result, single sign-on is fast becoming the preferred login option for organisations. 

This article provides high-level details of the alternatives available for configuring your Asset Bank so that users do not have to enter a username and password each time they start a new session. Please note that all of these options except the 'remember me' cookie require a professional/enterprise licence.

Note: SSO is a Professional / Enterprise license feature. Set-up fees apply. To enable SSO please contact our Customer Support Team.
 

Integration with a cloud-based SSO technology

There are many different SSO technologies available. Asset Bank’s authentication module has been designed so that we can easily develop new plugins to enable SSO (single sign-on) technologies to be used.

We have already developed plugins to enable Asset Bank to work with the following SSO technologies:

We can only configure one SAML 2.0 provider per site, however you can use multiple SSO methods alongside the default non-SSO (local) user logins if desired.
 

EncryptedURL Plugin

Asset Bank's ‘EncryptedUrlSSO’ plugin, enables a client's developers to show a link (e.g. on an Intranet) to Asset Bank that includes a user’s details encrypted and encoded, so Asset Bank can create them as a user (if it hasn’t seen them already) and log them in. See EncryptedUrlSSO Specification.

'Remember me' cookie

Asset Bank can show a 'Remember me' checkbox on the login page (this is turned off by default). If this functionality is enabled and a user checks the checkbox, an encrypted token is stored in a cookie so that Asset Bank can log them in automatically the next time they visit. No personal details about the user, other than the encrypted identifier, are stored in the cookie. Talk to our Customer Support Team for help enabling this.

Related articles

Comments

0 comments

Article is closed for comments.