Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 6.9 - Administration Guide

Introduction System requirements and versions Using API and PowerShell tools Using the virtual appliance and web management console Cloud deployment considerations Setting up Safeguard for Privileged Passwords for the first time Using the web client Getting started with the desktop client Using the desktop client Search box Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Discovery Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificates settings Cluster settings Enable or Disable Services settings External Integration settings Messaging settings (desktop client) Password Management settings Real-Time Reports Safeguard Access settings SSH Key Management settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP 2.7 or later migration guidance Appendix C: SPP and SPS join guidance Appendix D: Regular Expressions About us

Password fails for Unix host

Some Unix systems silently truncate passwords to their maximum allowed length. For example, Macintosh OS X only allows a password of 128 characters. If an Asset Administrator creates a profile with an Account Password Rule that sets the password length to 136 characters, when Safeguard for Privileged Passwords changes the password for an account governed by that profile, the asset's operating system truncates the new password to the allowable length and does not return an error; however, the full 136-character password is stored in Safeguard for Privileged Passwords. This causes the following issues:

  • Check Password for that account will fail. When Safeguard for Privileged Passwords compares the password on the Unix host with the password in Safeguard for Privileged Passwords, they never match because the Unix host truncated the password generated by Safeguard for Privileged Passwords.

  • A user will not be able to log in to the Unix host account successfully with the password provided by Safeguard for Privileged Passwords unless they truncate the password to the allowable length imposed by the operating system.

Password or SSH key is pending review

Safeguard for Privileged Passwords can resolve a situation when a user needs to request an account password or SSH key but cannot because there is a previous release request still in the Pending Review state and the designated reviewer is not available. If the request is left in this state, Safeguard for Privileged Passwords prevents users from checking out the account password or SSH key. In such a situation, the Security Policy Administrator can close the request without review.

You can also set up requests so that pending reviews do not block access. For more information, see Reviewer tab.

To close a password without review

  1. Log in as a user with Security Policy Administrator permissions.
  2. On the Home page, click Refresh.
  3. Open Administrator to review the pending request.
  4. Select Close Request.
  5. Type an explanation in the Comment box of up to 255 characters (required).
  6. Select Close Request.

You can query and view all requests closed without review in the Activity Center. Filter the events by Password Request Closed, then export the search results to see the old state and new state.

Related Topics

Password or SSH key is pending a reset

Password or SSH key is pending a reset

If a user receives a persistent message that states either of the following types of messages, the account password or SSH key is stuck in a pending password/SSH key change state:

  • You cannot checkout the password or SSH key for this account while another request is pending password or SSH key reset
  • This account has password or SSH key requests which have not yet expired or have to be reviewed. It cannot be deleted now"

Possible solutions:

  • Ensure that the service account for the asset associated with this account is working. Then manually change the account password or SSH key . See: Checking, changing, or setting an account password and Checking, changing, or setting an SSH key.
  • Or, if the service account for the asset is working properly and the policy governing the account allows emergency access and has enabled multiple users simultaneous access, you can instruct the user to request the password or SSH key using Emergency Access.

You can allow new access requests whether a prior request is approved or not approved. In other words, no requests will be blocked based on the approval status of a prior request. Setting the Pending reviews do not block access check box only pertains to future requests. For more information, see Reviewer tab.

Related Topics

Password or SSH key is pending review

Password or SSH key profile did not run

The password and SSH key management settings Settings | Access Request | Enable or Disable Services enable the automatic profile check and change schedules in partitions.

Ensure the password and SSH key management settings are enable for profiles to run on schedule:

  • Check Password Management Enabled
  • Change Password Management Enabled
  • Check SSH Key Management Enabled
  • Change SSH Key Management Enabled

For more information, see Enable or disable access request and services.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating