One Identity Safeguard for Privileged Sessions 6.4.0 - Administration Guide

Managing One Identity Safeguard for Privileged Sessions (SPS) users locally

By default, One Identity Safeguard for Privileged Sessions (SPS) users are managed locally on SPS. In order to add local users in SPS, all steps of the following procedure need to be completed:

1. Create users.

   For detailed instructions on how to create local users, see Creating local users in One Identity Safeguard for Privileged Sessions (SPS).

2. Assign users to groups.

   For details about how to add a usergroup, see Managing local usergroups.

3. Assign privileges to groups.

   For information on how to control the privileges of usergroups, see Managing user rights and usergroups.

Creating local users in One Identity Safeguard for Privileged Sessions (SPS)

The following describes how to create a local user.

To create a local user

1. Navigate to AAA > Local Users and click .

   Figure 67: AAA > Local Users — Creating local users

   

2. Enter the username into the User field.

   NOTE:

   For the username of SSH users, only valid UTF-8 strings are allowed.

   The following characters cannot be used in usernames: <>\/[]:;|=,+*?

3. Enter a password for the user into the Password and Verify password fields.

   The strength of the password is indicated below the Password field as you type. To set a policy for password strength, see Setting password policies for local users. The user can change the password later from the SPS web interface, and you can modify the password of the user here.

   Use strong passwords: at least 8 characters that include numbers, letters, special characters, and capital letters. For local One Identity Safeguard for Privileged Sessions (SPS) users, require the use of strong passwords (set AAA > Settings > Minimal password strength to strong). For details, see "Setting password policies for local users" in the Administration Guide.

   NOTE:

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

4. Click in the Groups section and select a group that the user will be member of. Repeat this step to add the user to multiple groups.

   If you wish to modify the group membership of a local user later on, you can do that here.

   To remove a user from a group, click next to the group.

5. Click .

Deleting a local user from One Identity Safeguard for Privileged Sessions (SPS)

The following describes how to delete a local user from One Identity Safeguard for Privileged Sessions (SPS).

To delete a local user from SPS

1. Navigate to AAA > Local Users.

2. Find the user you wish to delete.

3. Click next to the user, at the right edge of the screen.

4. Click .

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. Unicode characters as well as 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.