You can configure SAML 2.0 authentication using the Site authentication settings wizard of the Active Roles Configuration Center. For more information about how SAML 2.0 authentication works in Active Roles, see SAML 2.0 authentication in Active Roles in the Active Roles Feature Guide.
Prerequisites
To configure SAML 2.0 authentication, the following prerequisites must be met:
-
You must configure your SAML identity provider before configuring SAML 2.0 authentication in Active Roles. For more information, see Examples of configuring SAML identity providers.
-
To use SAML 2.0 authentication, you must have a valid SSL/TLS certificate configured for Active Roles.
To configure SAML 2.0 authentication in the Active Roles Configuration Center
-
In the Active Roles Configuration Center main window, click Web Interface.
The Web Interface page displays all the Active RolesWeb Interface sites that are deployed on the web server running the Active RolesWeb Interface.
-
To configure the authentication settings, click Authentication.
The Site authentication settings page appears.
NOTE: By default, the Windows authentication setting is configured.
-
To configure SAML 2.0 authentication, select SAML 2.0 and other protocols used for federated authentication, then click Next.
-
To complete the initial configuration of the Redistributable Secure Token Server (RSTS), enter a password in the Password and Confirm password fields, then click Configure RSTS.
NOTE:Port number and Administrator website URL are filled automatically.
NOTE: If RSTS is running, but not responsive, you can:
-
Click Try to fix.
-
Restart the Configuration Center.
TIP: To change the password, select Create new secret, enter a new password in the Password and Confirm Password fields, and click Configure RSTS.
-
-
To configure the identity provider, in Configure Provider, click Add.
NOTE: By default, Active Directory is available as an identity provider and it cannot be removed or modified.
-
For Authentication provider type, select External Federation.
NOTE: For Authentication provider type, the two options available are Active Directory and External Federation.
-
Enter the Display name for the SAML provider.
-
In Realm, enter the email suffix(es) of the user(s) who will authenticate with this provider, separated by space. For example: mysuffix.com mysuffix.net.
NOTE: This setting is only used if you have multiple External Federation providers configured, with none set as the Default Provider. This will allow RSTS to route users to the correct provider based on their email address.
-
(Optional) Enter the Application ID override.
NOTE: Application ID override is only required if you cannot enter the RSTS Entity ID (urn:RSTS/identity) in your SAML Application. In that case, set Application ID override to match the Entity ID of your SAML Application.
-
Enter the Federation metadata XML from your SAML provider. Using the toggle (set to From URL by default), you can specify whether to load the metadata from a URL, from a file, or paste it directly to the text box.
-
From URL: In Federation metadata URL, copy-paste the metadata URL.
NOTE: One Identity recommends linking the metadata from a URL, so that RSTS will automatically refresh it and keep the IdP signing certificate up-to-date.
-
From File: After selecting this option, click Load from file to load the metadata XML file, or copy-paste the metadata string into the text box.
NOTE: You can get the federation metadata after configuring the application in your SAML identity provider. For more information, see Examples of configuring SAML identity providers.
-
-
(Optional) To test the connection, click Test metadata. If the connection is successful, a confirmation message appears.
-
In the Associated Active Directory drop-down, keep Default Active Directory selected.
-
(Optional) To have all users authenticate with this SAML provider, select Set as default.
NOTE: One Identity recommends enabling this setting to require all users to authenticate with the SAML provider.
NOTE: If there is no default provider set, users will be redirected to a login page where they can select their provider.
-
To save your settings, click Save.
-
-
Click Next.
-
In Configure Claims, click Add.
-
For the Claim type, select GUID.
-
For the Claim value, select http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier.
The Display Name will appear as IUser.Id.
NOTE: The claims that Active Roles receives from RSTS come from the AD user account, not the SAML provider. The NameIdentifier claim will always contain the user’s objectGUID. One Identity recommends always using this mapping.
-
To save your settings, click Save.
-
-
Click Modify.
-
When the operation completes, click Finish.