To prepare Unix-based systems (AIX, HP-UX, Linux, Macintosh OS X, Solaris, and FreeBSD platforms)
Create a service account on the asset with sufficient permissions.
You need to at least configure a password for the service account. If you want to use an SSH key generated and configured by Safeguard for Privileged Passwords, then you also need to make sure the service account’s home directory exists.
Ensure that the service account can run the following list of commands with root privileges non-interactively; that is, without prompting for a password.
For example, on a Linux system add the following line in the sudoers file:
<SerAcctName> ALL=(root) NOPASSWD: /usr/bin/passwd
The commands a service account must run with root privileges non-interactively are:
Linux and most Unix-based systems:
Mac OS X
Enable and configure the SSH server to allow the service account to log in remotely. For example, on a Mac, enable Remote Login for the service account.
Note: Different versions of Linux and Unix may require slightly different parameters for SSH configuration. Consult a Linux/Unix system administrator or the system documentation for assistance.
Configure the system's firewall to allow the following predefined incoming rules:
Windows Management Instrumentation (WMI-In)
These rules allow incoming traffic on TCP port 135 and TCP SMB 445 respectively.
Port 389 is LDAP for connections. LDAP port 389 connections are used for Active Directory Asset Discovery and Directory Account Discovery.
Change the local security policy:
Before Safeguard for Privileged Passwords can reset local account passwords on Windows systems, using a service account that is a non-built-in administrator, you must change the local security policy to disable the User Account Control (UAC) Admin Approval Mode ("Run all administrators in Admin Approval Mode") option. For more information, see Change password fails.
For additional information on ports, see Appendix A: Safeguard ports.
The following minimum permissions are required for Windows assets to perform directory password management and sessions management tasks using Windows Management Instrumentation (WMI).
Using a local account or domain account:
Remote Activation permission on computer via DCOM.
To set Remote Enable and Enable Account permissions
To set Remote Activation permissions
Using a Domain account:
Using a local account:
Using a Domain account:
One Identity recommends the following resolutions to some of the common problems you might encounter as you deploy and use Safeguard for Privileged Passwords. For more information about how to troubleshoot Safeguard for Privileged Passwords, refer to the Appliance settings.