Single Sign On
Single Sign On (SSO) is where your internal server is responsible for authenticating users. Authentication in this context means that the username and password entered by the user is valid.
Here's how it works:
- The user enters the web address (URL) of their PoolCar system (or uses a bookmarked link).
- PoolCar silently redirects the user to the front page of your login server.
- The user enters their username and password and your server checks the details entered.
- If successful, your server then redirects the user back to the PoolCar server with a token.
- PoolCar sees this token and accepts that the user has been successfully authenticated by your server.
SSO provides the user with a user experience because they do not have to remember yet another username and password for a different system.
By integrating PoolCar with your SSO provider the user simply needs to enter their company-issued username and password. What's more, depending on your configuration, if the user is accessing PoolCar from within your organization's network, the login step will most likely be skipped because they have already authenticated to their laptop or desktop computer.
PoolCar supports and has successfully integrated with the following platforms:
- ADFS v2 and v3
- Azure AD (i.e. Office 365)
- SAML v2 and v3 (i.e. Ping Federate)
New Customer or Retro-Fit
For new customers who are implementing PoolCar for the first time, our on-boarding process addresses the inclusion of a Single Sign On activity. During this phase of the project, our IT people will liaise with your IT people to configure the security certificates and other technical details.
For existing customers, it is possible to migrate to an SSO model and retain all your user data. Please contact us for a quote to migrate your existing PoolCar user data to the new SSO model.