Setting up SSO Authentication
Single sign-on (SSO) is an authentication process that allows users to access multiple applications using a single username and password. The SSO solution frees the users from entering their usernames and password repeatedly when switching between applications. This topic provides details on how to set up SSO authentication for connecting to ALM.
If you upgrade ALM to 15.50 from an earlier verion with SSO enabled, to make sure SSO still works as expected, you should re-deploy the SSO components after the upgrade. For details, see Setting up SSO Authentication.
Note: For CAC (Common Access Card) and SiteMinder authentication, see the ALM External Authentication Configuration Guide.
ALM supports SSO via SAML 2.0 and acts as a service provider (SP) for SSO. Or it supports SSO via OpenID Connect (OIDC) and acts as a Relying Party (RP). You must implement a federation service to act as an identity provider (IdP) with federation protocol of SAML 2.0 or OIDC.
The ALM SSO solution works as follows:
- A user logs on to an application that can serve as the identity provider (IdP).
- The user requests the access to an ALM resource.
ALM sends an authentication request to the IdP to obtain the user information. With the user information, ALM attempts to locate a matching user for the IdP user in ALM and decides whether or not to grant the user the access to the ALM resource.
Scenario Description and result A matching user exists in ALM ALM checks the IdP user by Identity Key and IdP ID. If both of these are located to one ALM user, the IdP user is authorized. No matching user exists in ALM
The user is not authorized and cannot log in.
If auto user-provisioning is enabled, ALM will run the auto user-provisioning process to create or find a matching user in ALM. For details, see Setting up SSO Authentication.
How to set up SSO authentication
Follow the steps below one by one to complete the SSO configuration.