Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 6.5.0 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings MSSQL-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS) Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

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 Users & Access Control > Settings.

    Figure 68: Users & Access Control > 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 Commit.

    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.

Related Documents