One Identity Safeguard for Privileged Sessions 7.0.5.1 LTS

The One Identity Safeguard for Privileged Sessions (SPS) web interface can authenticate users to an external LDAP database to simplify the integration of SPS to your existing infrastructure. You can also specify multiple LDAP servers, so that if the first server becomes unavailable, SPS can try to connect to another server.

NOTE: Consider the following:

Local users, including the admin user, are available by default.
The admin user has every privilege and cannot be deleted.
SPS accepts both pre-Windows 2000 style and Windows 2003 style User Principal Names (UPNs). UPNs consist of a username, the at (@) character, and a domain name, for example administrator@example.com.
For SSH usernames, SPS supports only valid UTF-8 strings.
The following characters cannot be used in:
- user names: /\[]:;|=+*?<>"
- group names: /\[]:;|=+*?<>"@,
When using RADIUS authentication with LDAP users, the users are authenticated to the RADIUS server; however, their group memberships are managed in LDAP. For details, see Authenticating users to a RADIUS server in the Administration Guide.
If the matching rule for an attribute is case insensitive in the LDAP database, SPS treats user names and group names in a case insensitive manner.

Prerequisites

Make sure that the response timeout of the LDAP/Active Directory server is set to a minimum of 120 seconds.

To configure an LDAP server

Navigate to Users & Access Control > Login options > Manage AD/LDAP Servers.
Select the LDAP server from the list. Alternatively, if no LDAP server exists yet, click Add new server and select the server type you want to create:
- Active directory
  
  For more information, see Adding a new Active Directory server.
- POSIX LDAP
  
  For more information, see Adding a new POSIX LDAP server.

POSIX LDAP backend

NOTE: Consider the following:

Local users, including the admin user, are available by default.
The admin user has every privilege and cannot be deleted.
SPS accepts both pre-Windows 2000 style and Windows 2003 style User Principal Names (UPNs). UPNs consist of a username, the at (@) character, and a domain name, for example administrator@example.com.
For SSH usernames, SPS supports only valid UTF-8 strings.
The following characters cannot be used in:
- user names: /\[]:;|=+*?<>"
- group names: /\[]:;|=+*?<>"@,
When using RADIUS authentication with LDAP users, the users are authenticated to the RADIUS server; however, their group memberships are managed in LDAP. For details, see Authenticating users to a RADIUS server in the Administration Guide.
If the matching rule for an attribute is case insensitive in the LDAP database, SPS treats user names and group names in a case insensitive manner.

Prerequisites

Make sure that the response timeout of the LDAP/Active Directory server is set to a minimum of 120 seconds.

To configure an LDAP server

Navigate to Users & Access Control > Login options > Manage AD/LDAP Servers.
Select the LDAP server from the list. Alternatively, if no LDAP server exists yet, click Add new server and select the server type you want to create:
- Active directory
  
  For more information, see Adding a new Active Directory server.
- POSIX LDAP
  
  For more information, see Adding a new POSIX LDAP server.

Authenticating users to a RADIUS server

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:
- Select an existing RADIUS login option and click Edit.
- Click Create new authentication method and select RADIUS.
The following figure shows the configuration options of the RADIUS login method.

Figure 86: 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.
1. In the Address field, enter the IP address or domain name of the RADIUS server. Use an IPv4 address or hostname.
2. In the Server port field, enter the port number.
3. 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:
  - Letters A-Z, a-z
  - Numbers 0-9
  - The space character
  - Special characters: !"#$%&'()*+,-./:;<>=?@[]\^-`{}_|
4. 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:
- Active Directory
  
  For more information, see Adding a new Active Directory server.
- POSIX
  
  For more information, see Adding a new POSIX LDAP server.
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.

Authenticating users with X.509 certificates

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).

Prerequisites

Navigate to Basic Settings > Trust Stores and create a custom trust store. For more information, see Verifying certificates with Certificate Authorities using trust stores.

Figure 87: Basic Settings > Trust Stores— Creating a custom trust store

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:
- Select an existing X.509 login option and click Edit.
- Click Create new authentication method and select X.509.
The following figure shows the configuration options of the X.509 login method.

Figure 88: 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:
- Active Directory
  
  For more information, see Adding a new Active Directory server.
- POSIX
  
  For more information, see Adding a new POSIX LDAP server.
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.

One Identity Safeguard for Privileged Sessions 7.0.5.1 LTS - Administration Guide

Active Directory LDAP backend

Prerequisites

POSIX LDAP backend

Prerequisites

Authenticating users to a RADIUS server

Authenticating SPS users to a RADIUS server

Authenticating users with X.509 certificates

Prerequisites

Authenticating SPS users on the SPS interface with X.509 certificates

製品を選択してください:

サービス向上のために、「Purpose of your Chat（チャットの目的）」を記入してください。

お客様の不具合に推奨されるソリューション

One Identity Safeguard for Privileged Sessions 7.0.5.1 LTS - Administration Guide

Active Directory LDAP backend

Prerequisites

POSIX LDAP backend

Prerequisites

Authenticating users to a RADIUS server

Authenticating SPS users to a RADIUS server

Authenticating users with X.509 certificates

Prerequisites

Authenticating SPS users on the SPS interface with X.509 certificates