Configuring a Single Sign-On Server
Use this page to configure a single sign-on server (SSO) that is used for authenticating users. Starting from CSO Release 6.2.0, tenants can configure their own SSO server to authenticate their users.
There are two entities involved during the SSO configuration:
-
SSO Server or Identity Provider—An external server integrated with CSO.
-
OpCo or Tenant—Acts as an service provider and receives the SAML assertion sent by the SSO server in a response to a login request.
Both the identity provider and OpCo or tenant trust each other and configuration is required for both the entities. Two use cases are possible:
-
Identity provider is configured first before SSO server is added in CSO—The identity provider is configured first. Then, at the OpCo level, you can add the SSO server in CSO for tenant users, and enter the server name and metadata URL.
-
IdP is configured after SSO server is added in CSO—Enter the SSO server name and then click the Next button. CSO provides a list of URLs to be configured in the identity provider. After the identity provider is configured with the URLs, you can edit the SSO server name and enter the metadata URL.
For both the use cases, the metadata URL is required before you use the SSO server.
To configure an SSO server:
Field |
Description |
---|---|
Basic Information | |
SSO Server Name |
Specify the name of the SSO server. You can use a string of alphanumeric characters, special characters such as the underscore (_) or the period (.), and spaces. The maximum length is 40 characters. |
Description |
Enter a meaningful description for the SSO server. |
Metadata File |
Click Browse to navigate to the file location in your local system and select the SSO server metadata XML file to upload. Note:
Starting in CSO Release 6.3.0, you can either import the SSO server metadata XML file directly into CSO or provide the metadata URL. |
Metadata URL |
Enter the URL from where the SSO server metadata needs to be downloaded. If you uploaded a metadata file, the URL is automatically generated. |
User Identification |
Specify how a user is identified from the SAML assertion:
Note:
If you are using Microsoft Azure as the IdP, we recommend that you use the SAML attribute for user identification. Tenant users might face authentication issues if you configure Name ID as the user identification attribute. |
Field | Description |
---|---|
SAML URLs |
CSO displays the SAML URL settings. The administrator uses this information to configure the IdP. |
Single Sign-On URL |
Displays the SAML Assertion Consumer Service (ACS) URL for the application. Example: https://aaa-example.com/ssol/sso server name/SAML2/POST |
Audience URI (SP Entity ID) |
Displays the service provider entity ID of the application. Example: https://aaa-example.com/Shibboleth |
Metadata URL |
Displays the metadata URL of the application. Example: https://aaa-example.com/saml/metadata/64000 |
Single Logout URL |
Displays the single logout URL of the application. Example: https://aaa-example.com/splogout |
Download Metadata |
Click this option to download metadata from the application. The administrator can download the CSO metadata and use the metadata to configure the identity provider instead configuring individual identity provider fields at a time. |
Download Certificate |
Click this option to download the SAML certificate from the application. The administrator can use this certificate to update the certificate on the identity provider. |