One Identity Safeguard for Privileged Sessions (SPS) can authenticate its users to an external RADIUS server. Group memberships of the users must be managed either locally on SPS or in an LDAP database.
|
|
Caution:
The challenge/response authentication method is currently not supported. Use other authentication methods (for example password, SecureID). |
Authenticating SPS users to a RADIUS server
To authenticate SPS users to a RADIUS server, complete the following steps.
-
Navigate to Users & Access Control > Login Options.
-
To configure a RADIUS login method, select one of the following options:
The following figure shows the configuration options of the RADIUS login method.
Figure 87: Users & Access Control > Login options — Configuring RADIUS authentication
-
In the Name field, specify a name for the login option.
-
(Optional) Enable the RADIUS login method.
-
To add a new RADIUS server, click Create new RADIUS server.
-
In the Address field, enter the IP address or domain name of the RADIUS server. Use an IPv4 address or hostname.
-
In the Server port field, enter the port number.
-
In the Shared secret field, enter the password that SPS can use to access the RADIUS server.
NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:
-
Click Save.
-
(Optional) To add more RADIUS servers, click 
and repeat the procedure for adding a new RADIUS server.
If a server is unreachable, SPS tries to connect to the next server in the list in failover mode.
-
Select the authentication protocol.
-
To use the Password Authentication Protocol, select PAP.
-
To use the Challenge-Handshake Authentication Protocol, select CHAP.
-
Select LDAP server or Local as the Authorization Backend.
-
(Optional) To add a new LDAP server, click New LDAP server under Authorization backend and select one of the server types:
-
Script reference is filled out automatically when you specify the name for the login option. Special characters are automatically replaced with dashes ("-"). The Script name is a unique, human readable ID that is used by the REST API clients to select the login method.
-
To save your modifications, click Commit.
|
|
Caution:
After you commit this configuration, the SPS web interface will be available only after successfully authenticating to the RADIUS server. Note that the default admin account of SPS will be able to login normally, even if the RADIUS server is unaccessible. |
One Identity Safeguard for Privileged Sessions (SPS) provides a method to authenticate the users of the web interface with X.509 client certificates. The client certificate is validated against a trust store, and the username is exported from the client certificate for identification.
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
Authenticating SPS users on the SPS interface with X.509 certificates
To authenticate SPS users on the SPS web interface with X.509 client certificates, complete the following steps.
-
Navigate to Users & Access Control > Login options.
-
To configure an X.509 login method, select one of the following options:
The following figure shows the configuration options of the X.509 login method.
Figure 89: Users & Access Control > Login options — Configuring X.509 authentication
-
In the Name field, specify a name for the login option.
-
(Optional) Enable the X.509 login method.
NOTE: You can enable only one X.509 login method at a time.
-
Select the trust store you created as a prerequisite in Basic Settings > Trust Stores.
|
|
CAUTION: From version 6.8, SPS changes authenticating the users of the web interface with X.509 client certificates: certificates are validated against a trust store instead of a trusted CA list. During the upgrade, the trusted CA list formerly used for authentication is copied to a trust store that has revocation check disabled by default.
If you have previously enabled revocation check for your trusted CA list and already added the URLs of Certificate Revocation Lists (CRL), or you want to enable revocation check, you must edit the trust store settings manually.
-
Navigate to Basic Settings > Trust Stores.
-
Select the revocation check type Leaf or Full for the trust store.
-
Add a CRL URL for each root and intermediate CA.
For more information about trust stores and how to configure them, see "Verifying certificates with Certificate Authorities using trust stores" in the Administration Guide. |
-
In the Certificate attribute field, select the user certificate field that contains the username. In most cases, it is the commonName or userid field, but SPS supports the emailAddress and userPrincipalName fields as well.
-
Select LDAP server or Local as the Authorization Backend.
-
(Optional) To add a new LDAP server, click New LDAP server under Authorization backend and select one of the server types:
-
Script reference is filled out automatically when you specify the name for the login option. Special characters are automatically replaced with dashes ("-"). The Script name is a unique, human readable ID that is used by the REST API clients to select the login method.
-
To save your modifications, click Commit.
The topics below discuss how to authenticate users with SAML2.
During SAML2 login, the Service Provider (SP) makes the authorization decision about a subject (user) based on an assertion, which is created by an Identity Provider (IdP). To make this decision, the SP must trust the IdP and the IdP must provide enough information about the user to make this authorization decision.
When you configure SAML2 login in One Identity Safeguard for Privileged Sessions, SPS serves as the SP. The SAML2 authentication flow consists of several HTTP redirects, where the information exchange between the SP and the IdP is performed using the user's browser. This means that there is no direct network communication between SPS and the IdP.
The process of the SAML2 authentication flow is the following:
- The user goes to the SPS login page and clicks on the login button associated with your SAML2 login method, see Authenticating users with SAML2 login method for the details.
- SPS redirects the user to the login page of the IdP. The redirect contains the SAML2 authentication request.
- The IdP authenticates the user. This step is entirely within the domain of the IdP. It may require a password and/or a second factor, or, if the user has an active session at a different application, the authentication may be performed without any user interaction, providing a single sign-on experience.
- The IdP redirects the user back to SPS. This redirect conveys the SAML2 response, which contains information about the user.
- SPS processes the response and based on the information within, it maps the user either to a local or to an AD/LDAP user entry. If the IdP provides the user's groups in the response, then SPS evaluates the permissions assigned to the groups given by the IdP. Otherwise, the permissions are evaluated based on the groups in which the mapped local or AD/LDAP user entry is a member.
