One Identity Safeguard 2.5 - Administration Guide

Introduction System requirements Installing the One Identity Safeguard for Privileged Passwords desktop client Setting up Safeguard for Privileged Passwords for the first time Getting acquainted with the console Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Directories Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificate settings Cluster settings External Integration settings Messaging settings Profile settings Access settings Sessions settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions
How do I access the API How do I audit transaction activity How do I configure external federation authentication How do I manage accounts on unsupported platforms How do I modify the appliance configuration settings How do I prevent Safeguard for Privileged Passwords messages when making RDP connections How do I see which assets and/or accounts are governed by a profile How do I set the appliance system time How do I setup discovery jobs How do Safeguard for Privileged Passwords database servers use SSL What are the access request states What do I do when an appliance goes into quarantine What is required for One Identity Safeguard for Privileged Passwords, embedded sessions module What is required to integrate with Starling Identity Analytics & Risk Intelligence What needs to be set up to use Application to Application What role-based email notifications are generated by default When does the rules engine run for dynamic grouping and tagging Why did the password change during an open request Why join Safeguard for Privileged Passwords to One Identity Starling
Safeguard Desktop Player Appendix: Safeguard ports

Prepare SAP Netweaver Application Servers

Safeguard for Privileged Passwords makes an SSL connection to the SAP Application Server using a TCP port between 3300 and 3399, depending on the SAP system number (also known as the "instance number").

Note: You can have multiple instances of SAP running on a server, each using a different network port in the range 3300-3399. The last two digits of the port are called the system number (or instance number). Also, when you assign a password to the account, the account is not usable until you log in and change the password from the admin-assigned value.

Note: If a privileged user for the asset is of Dialog User or Communication Data type, assign RFC authorization for the RFCPING function module for that user. This allows the user to execute its functions remotely, such as changing the password.

To configure a SAP Netweaver Application Server for Safeguard for Privileged Passwords

  1. Create a service account and assign it a password.

    Note: This service account must have permissions for remote connections and permissions to change passwords. For example, S_A.SYSTEM or SAP_ALL authorization profiles will work, but may have more permissions than are necessary. Consult your SAP security guide for the appropriate settings for your organization.

  2. Verify that you can log in with the service account.

    Note: In SAP, when you create a new account of Dialog User or Communication Data type, you will be prompted to set a new password.

  3. In Safeguard for Privileged Passwords, create the asset and accounts for the SAP asset type using password authentication. You must specify the SAP Client ID number as well as the Port used by the SAP instance.

    Note: When you create an account of Dialog User or Communication Data type, Safeguard allows you to set the account password or reset the password. Use the Reset Password option to reset the password for this account. If you use the Set Password option and enter the same password used in SAP, the password check in Safeguard will fail.

Prepare Sybase (Adaptive Server Enterprise) servers

To prepare a Sybase ASE (Adaptive Server Enterprise) server for Safeguard for Privileged Passwords, refer to the documentation for your Sybase ASE server for information about how to setup and secure encryption.

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 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.

Prepare SonicOS devices

Safeguard for Privileged Passwords supports SonicOS Internet appliances. Safeguard for Privileged Passwords uses the SSH protocol to connect to SonicOS devices.

To prepare a SonicOS device for Safeguard for Privileged Passwords

  1. Create the service account as a local user on the managed system and assign it a password.
  2. Add the service account to the SonicWALL Administrators group. This allows the service account to access the device with SSH to manage users.

    Important: Safeguard for Privileged Passwords can only manage passwords for users that are members of the SonicWALL Administrators group.

  3. Enable and configure the SSH server to allow the service account to log in remotely.
  4. Add the SonicOS device to Safeguard for Privileged Passwords using password authentication.

Prepare SonicWALL SMA or CMS appliances

Here are some important notes about configuring a SonicWALL SMA or CMS appliance for Safeguard for Privileged Passwords:

  1. Use the local "admin" account as the service account.
  2. Safeguard for Privileged Passwords can only manage the admin account; it cannot manage other local accounts or accounts from external providers.
Related Documents