Single Sign-On (SSO) Requirements
This article will describe the basic information on the Single Sign On (SSO) authentication method and the requirements to deploy it on your domain.
The single sign-on (SSO) authentication method allows your Platform users to securely log in by using your own enterprise identity provider.
Platform users will be able to use their enterprise credentials.
2. How does it work?
In the Alteia Platform, the SSO is configured per domain, and there is no “role mapping” done with the enterprise identity provider (IDP), which means that users on the enterprise IDP do not have default access.
Users with “Manager” rights still grant access to other users, by mail invitation, and define which roles, organizations, companies, and projects are available to each user.
Alteia Platform delegates the authentication to the enterprise identity provider (IDP), so there is no pre-authenticated login page.
3. Supported IDP protocols & requirements
The enterprise identity provider (IDP) must support:
- Open ID Connect (OIDC) protocol.
- Claims for first name, last name, and email - Corresponding to the “openID profile email” basic OIDP scopes.
4. Configuring the solution with Open ID Connect (OIDC)
There are two required steps to configure the SSO with Open ID Connect (OIDC) protocol:
- On the Alteia-based system side:
- Instances with the additional SSO modules/components deployed and configured
- “Redirect URI” or response URL endpoint configured on the SSO-enables domains (To be configured on the enterprise IDP side)
- From the enterprise IDP side (as output, to be configured on the Alteia-based system side):
- Client’s ID
- Client’s secret*
- OAuth2/OIDC endpoints**