One Identity Safeguard for Privileged Sessions 6.0.6 - Administration Guide

Setting password policies for local users

One Identity Safeguard for Privileged Sessions (SPS) can use password policies to enforce minimal password strength and password expiry.

Limitations

Note the following important points about password policies.

• Password policies do not apply to the built-in admin user.

• Password policies apply only for locally managed users, and have no effect if you manage your users from an LDAP database, or if you authenticate your users to a RADIUS server.

  NOTE: One Identity Safeguard for Privileged Sessions (SPS) accepts passwords that are not longer than 150 characters. The following special characters can be used: !"#$%&'()*+,-./:;<=>?@[\]^-`{|}

To create a password policy

1. Navigate to AAA > Settings.

   Figure 68: AAA > Settings — Configuring password policies

   

2. Verify that the Authentication method is set to Password provided by database and that the User database is set to Local.

   NOTE: If the setting of these fields is different (for example LDAP or RADIUS), then SPS is not configured to manage passwords locally.

3. Set how long the passwords are valid in the Password expiration field. After this period, SPS users will have to change their password. To disable password expiry, enter 0.

4. To prevent password-reuse (for example when a user has two password and instead of changing to a new password only switches between the two), set how many different passwords must the user use before reusing an old password.

5. To enforce the use of strong password, select the level of password-complexity from the Minimal password strength field.

   NOTE: The strength of the password is determined by its entropy: the variety of numbers, letters, capital letters, and special characters used, not only by its length. To execute some simple dictionary-based attacks to find weak passwords, set Cracklib (eg. dictionary) check on password to Enabled.

6. Click .

   NOTE: Changes to the password policy do not affect existing passwords. However, setting password expiry will require every user to change their passwords after the expiry date, and the new passwords must comply with the strength requirements set in the password policy.

Managing local usergroups

You can use local groups to control the privileges of One Identity Safeguard for Privileged Sessions (SPS) local users — who can view and configure what.

For the description of built-in groups, see Built-in usergroups of One Identity Safeguard for Privileged Sessions (SPS).

Use the AAA > Group Management page to:

• Create a new usergroup.

• Display which users belong to a particular local usergroup.

• Edit group memberships.

To create a new group,

1. Navigate to AAA > Group Management and click .

   Figure 69: AAA > Group Management — Group management

   

   

2. Enter a name for the group.

3. Enter the names of the users belonging to the group. Click to add more users.

4. Click .

   Once you have added your usergroups, the next step is to start assigning privileges to them. For details on how to do that, see Assigning privileges to usergroups for the One Identity Safeguard for Privileged Sessions (SPS) web interface.

Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database

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: if the first server is unavailable, SPS will try to connect to the second server.

To enable LDAP authentication

1. Navigate to AAA > Settings > Authentication settings.

2. Select the LDAP option and enter the parameters of your LDAP server.

   Figure 70: AAA > Settings > Authentication settings — Configuring LDAP authentication

   

3. Enter the IP address or hostname and port of the LDAP server into the Server Address field. If you want to encrypt the communication between SPS and the LDAP server, in case of TLS, enter 636 as the port number, or in case of STARTTLS, enter 389 as the port number.

   Use an IPv4 address.

   To add multiple servers, click and enter the address of the next server. If a server is unreachable, SPS will try to connect to the next server in the list in failover fashion.

   Caution: If you will use a TLS-encrypted with certificate verification to connect to the LDAP server, use the full domain name (for example ldap.example.com) in the Server Address field, otherwise the certificate verification might fail. The name of the LDAP server must appear in the Common Name of the certificate.

4. Select the type of your LDAP server in the Type field. Select:

   • Active Directory to connect to Microsoft Active Directory servers.

     You can enable nested groups. Select Enable AD group membership check, then Enable nested groups.

     Caution: Nested groups can slow down the query and cause the connection to timeout if the LDAP tree is very large. In this case, disable the Enable nested groups option.

     To also check group membership based on group DNs in a user attribute, select Enable checking for group DNs in user objects and enter the name of the user attribute, for example, memberOf in the User attribute of group DNs field.

     Caution: Using this option significantly slows down log on to the SPS web interface if you have too many groups. Only use this option if you have an LDAP schema where the user groups can only be determined from a user attribute that contains the group DNs.

     To check for group membership based on user DNs in group attributes, use the Check the user DN in these groups options.

     For more information, see Active Directory LDAP backend.

   • POSIX to connect to servers that use the POSIX LDAP scheme.

     If your LDAP server uses a custom POSIX LDAP scheme, you might need to set which LDAP attributes store the username, or the attributes that set group memberships. For example, if your LDAP scheme does not use the uid attribute to store the usernames, set the Username (user ID) attribute name option.

     In addition to the primary group membership checking, you can allow checking for supplementary group memberships by selecting the Enable POSIX group membership check and specifying the POSIX group membership attribute name field.

     To also check group membership based on group DNs in a user attribute, select Enable checking for group DNs in user objects and enter the name of the user attribute, for example, memberOf in the User attribute of group DNs field and objectClass, for example, groupOfNames in the Group objectClass field.

     Caution: Using this option significantly slows down log on to the SPS web interface if you have too many groups. Only use this option if you have an LDAP schema where the user groups can only be determined from a user attribute that contains the group DNs.

     To check for group membership based on user DNs in group attributes, use the Check the user DN in these groups options.

     For more information, see POSIX LDAP backend.

     For an overview about LDAP user and group resolution in SPS, see Overview.

5. In the User Base DN field, enter the name of the DN to be used as the base of queries regarding users (for example: OU=People,DC=demodomain,DC=exampleinc).

   NOTE: You must fill in this field. It is OK to use the same value for User Base DN and Group Base DN. However, note that specifying a sufficiently narrow base for the LDAP subtrees where users and groups are stored can speed up LDAP operations.

6. In the Group Base DN field, enter the name of the DN to be used as the base of queries regarding groups (for example: OU=Groups,DC=demodomain,DC=exampleinc).

   NOTE: You must fill in this field. It is OK to use the same value for User Base DN and Group Base DN. However, note that specifying a sufficiently narrow base for the LDAP subtrees where users and groups are stored can speed up LDAP operations.

7. In the Bind DN field, enter the Distinguished Name that SPS should use to bind to the LDAP directory (for example: CN=Administrator,DC=demodomain,DC=exampleinc).

   NOTE: SPS accepts both pre-win2000-style and Win2003-style account names (User Principal Names), for example administrator@example.com is also accepted.

8. To configure or change the password to use when binding to the LDAP server, click Change and enter the password. Click Update. Click .

   NOTE: One Identity Safeguard for Privileged Sessions (SPS) accepts passwords that are not longer than 150 characters. The following special characters can be used: !"#$%&'()*+,-./:;<=>?@[\]^-`{|}

9. If you want to encrypt the communication between SPS and the LDAP server, in Encryption, select the TLS or the STARTTLS option and complete the following steps:

   Figure 71: Policies > LDAP Servers — Configuring encryption

   

   NOTE: TLS-encrypted connection to Microsoft Active Directory is supported only on Windows 2003 Server and newer platforms. Windows 2000 Server is not supported.

   • If you want SPS to verify the certificate of the server, select Only accept certificates issued by the specified CA certificate and click the icon in the CA X.509 certificate field. A pop-up window is displayed.

     Click Browse, select the certificate of the Certificate Authority (CA) that issued the certificate of the LDAP server, then click Upload. Alternatively, you can paste the certificate into the Copy-paste field and click Set.

     SPS will use this CA certificate to verify the certificate of the server, and reject the connections if the verification fails.

     Caution: According to recent cryptographic research, SHA-1 algorithm cannot be trusted as secure anymore, because signatures can be forged with reasonable costs. As a result, SHA-1 algorithm is not supported in SPS for X.509 certificate chains. Starting from SPS versions 6.0.4 and 6.5.0, certificates with SHA1-based signatures are no longer trusted for Active Directory or LDAP authentication, and future versions might refuse to validate SHA-1 signatures altogether. Note that Root CA certificates may still contain SHA-1 signatures, because the signature is not validated for self-signed certificates. It is expected that other software such as clients and servers connected to SPS might reject SHA-1 signatures in a similar fashion. Signing CAs in SPS generate certificates with SHA-256 since versions 4.3.4 and 5.0.0.

     Caution: If you will use a TLS-encrypted with certificate verification to connect to the LDAP server, use the full domain name (for example ldap.example.com) in the Server Address field, otherwise the certificate verification might fail. The name of the LDAP server must appear in the Common Name of the certificate.

   • If the LDAP server requires mutual authentication, that is, it expects a certificate from SPS, enable Authenticate as client. Generate and sign a certificate for SPS, then click in the Client X.509 certificate field to upload the certificate. After that, click in the Client key field and upload the private key corresponding to the certificate.

   One Identity recommends using 2048-bit RSA keys (or stronger).

10. Click .

    NOTE: You also have to configure the usergroups in SPS and possibly in your LDAP database. For details on using usergroups, see Using usergroups.

11. Click Test to test the connection.

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.

To authenticate SPS users to a RADIUS server

1. Navigate to AAA > Settings.

   Figure 72: Configuring RADIUS authentication

   

2. Set the Authentication method field to RADIUS.

   The status information displayed ([NOT CONFIGURED] and [CONFIGURED]) indicates whether or not you have provided the shared secret required to access the RADIUS server.

3. Enter the IP address or domain name of the RADIUS server into the Address field.

   Use an IPv4 address.

4. Click Change, and enter the password that SPS can use to access the server into the Shared secret field.

   NOTE: One Identity Safeguard for Privileged Sessions (SPS) accepts passwords that are not longer than 150 characters. The following special characters can be used: !"#$%&'()*+,-./:;<=>?@[\]^-`{|}

   Click Update.

5. To use the Password Authentication Protocol, select PAP. To use the Challenge-Handshake Authentication Protocol, select CHAP.

6. To add more RADIUS servers, click and repeat Steps 2-4.

   Repeat this step to add multiple servers. If a server is unreachable, SPS will try to connect to the next server in the list in failover fashion.

7. When configuring RADIUS authentication with locally managed user accounts, complete the following steps.

   1. Set Password expiration to 0.

   2. Set Number of passwords to remember to 0.

   3. Set Minimal password strength to disabled.

   4. Set Cracklib check on password to disabled.

8. Click .

   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.