- Use the local admin account as the service account.
- Safeguard for Privileged Passwords can only manage the admin account; it cannot manage other local accounts or accounts from external providers.
To enable SSL server certificate validation, add the server’s signing authority certificate to the Trusted Certificates store in Safeguard for Privileged Passwords. For more information, see Trusted CA Certificates.
For more information about how Safeguard for Privileged Passwords database servers use SSL, see How do Safeguard for Privileged Passwords database servers use SSL.
To configure a SQL Server for Safeguard for Privileged Passwords (with an authentication type of Local System Account)
Add other accounts as needed.
Save the asset.
On the Connection tab:
Service Account: Click Select Account and select a local system account from the list.
The accounts available for selection are Windows accounts that are linked to the Windows asset you added in Step 3.
Save the asset.
To configure a SQL Server for Safeguard for Privileged Passwords (with an authentication type of Directory Account)
On the Connection tab, complete the following:
Service Account: Click Select Account and select a domain user account from the list.
The accounts available for selection are domain user accounts that are linked to the directory you added in Step 1.
Safeguard for Privileged Passwords can manage authorized Top Secret users who have a valid accessor ID (ACID) with the facility TSO who can log on to the TSO interface.
This applies to both Top Secret mainframe and Top Secret mainframe LDAP platforms.
Note: Please refer to your IBM z/OS system documentation for details on installing and configuring the telnet server (and SSL).
Safeguard for Privileged Passwords automatically accepts any server certificate that the connection offers and does not verify the trust chain on the telnet certificate. In addition, Safeguard for Privileged Passwords does not support client certificate selection, so if telnet requires that the client present a certificate that is signed by a recognized authority, Safeguard for Privileged Passwords cannot support that configuration.
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 or SSH key 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.