Service account has insufficient privileges
If you are having service account issues, consider the following:
- Is the service account properly authorized to access the system? In a common setup, sudo is used to elevate the service account's privileges on the system.
- Has the service account been locked out or disabled?
- Is the service account configured to allow remote logon?
A service account needs sufficient permissions to edit the passwords of other accounts. For more information, see About service accounts.
To resolve incorrect or insufficient service account privileges
- Verify that the service account has sufficient permissions on the asset.
- Perform Test Connection to verify connection.
- Attempt to manually check, change, and set password or SSH key again on the account that failed.
If the asset is running a Windows operating system, a local account password or SSH key check, change, or set can fail when you are using an asset that is configured with a service account with Administrative privileges, other than the built-in Administrator.
Before Safeguard for Privileged Passwords can change local account passwords or SSH keys on Windows systems, using a service account that is a non-built-in administrator, you must change the local security policy to disable the Run all administrators in Admin Approval Mode option. For more information, see Change password or SSH key fails.
Cannot connect to remote machine through SSH or RDP
If you are unable to connect to a remote machine either through SSH or RDP, log in to the Safeguard for Privileged Passwords desktop client as an Appliance Administrator and check the Activity Center and logs for additional information.
Cannot delete account
If you are unable to delete an account, review the considerations below.
Wrong account name:
As an Asset Administrator, you may receive this error if you attempt to delete an account : This entity has access requests which have not yet expired or have to be reviewed. It cannot be deleted now. This error could indicate that Safeguard for Privileged Passwords is trying to change the password or SSH key on an account that does not exist on the asset.
One reason for this error message is that the wrong account name was used when adding the account to Safeguard. So now when someone requests the password or SSH key for this account, Safeguard displays the password or SSH key that was manually set. However, when the requester attempts to log in to the asset using the bad account and password or SSH key, it will fail. If the access request policy specified Change password after check-in, the above error message appears when the administrator tries to delete the account from Safeguard for Privileged Passwords.
Workaround: To delete the account with the misspelled name, first manually set the password or SSH key on the account. Once the account password is reset, Safeguard for Privileged Passwords will allow you to delete the account.
For more information, see:
Cannot play session message
If you receive a message that says Cannot play session... The specified executable is not a valid application for this OS platform, you are most likely attempting to run the Desktop Player on a 32-bit platform, which is not supported.