立即与支持人员聊天
与支持团队交流

One Identity Safeguard for Privileged Passwords 7.1 - 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 Home Privileged access requests Appliance Management
Appliance Backup and Retention Certificates Cluster Enable or Disable Services External Integration Real-Time Reports Safeguard Access Appliance Management Settings
Asset Management
Account Automation Accounts Assets Partitions Discovery Profiles Tags Registered Connectors Custom platforms
Security Policy Management
Access Request Activity Account Groups Application to Application Cloud Assistant Asset Groups Entitlements Linked Accounts User Groups Security Policy Settings
User Management Reports Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP and SPS join guidance Appendix C: Regular Expressions About us

Preparing PostgreSQL

Safeguard for Privileged Passwords makes an SSL connection to PostgreSQL using a TCP port defined in the postgresql.conf file. You must enter this port number when adding a PostgreSQL asset to Safeguard for Privileged Passwords.

To configure PostgreSQL for Safeguard for Privileged Passwords

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

    NOTE: The service account must have permissions for remote connections, modify log_statements (if you want to enable the Hide Alter User command from verbose log_statement logging option), and permissions to change passwords.

    Alter User commands can be excluded from the PostgreSQL server logs during Safeguard for Privileged Passwords password changes. The option to hide Alter User commands is enabled by default for new PostgreSQL assets starting with Safeguard for Privileged Passwords 7.1 with verbose log_statement logging. Customers upgrading to 7.1 that want to enable the option will need to reconfigure any existing PostgreSQL assets with verbose log_statement logging to have a service account with superuser permissions and enable the option.

    Consult your PostgreSQL Security Guide for the appropriate settings for your organization.

  2. Verify that you can log in with the service account.
  3. In Safeguard for Privileged Passwords, create the asset and accounts for the PostgreSQL asset type using password authentication. You must specify the Database instance name and the Port used by the database instance.

    NOTE: When you create an account of Dialog User or Communication Data type, Safeguard for Privileged Passwords 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 PostgreSQL, the password check in Safeguard for Privileged Passwords will fail.

Preparing RACF mainframe systems

This applies to both RACF mainframe and RACF mainframe LDAP platforms.

To prepare IBM RACF mainframe systems for Safeguard for Privileged Passwords

  1. Create a service account on the asset and assign it a password.
  2. Grant the service account the privileges required to use the ALTERUSER command on other profiles.
  3. If not already installed, install a telnet server on the z/OS system. If required, secure telnet with SSL.

    NOTE: Please refer to your IBM z/OS system documentation for details on installing and configuring the telnet server (and SSL).

  4. Test the telnet server using a Windows-based 3270 emulator or on Linux, use the telnet-ssl or x3270 programs to test SSL and non-SSL connections to an z/OS system.
  5. In Safeguard for Privileged Passwords, create the asset and accounts for the z/OS system using password authentication.
About certificate support for the telnet protocol

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.

Preparing SAP HANA

Safeguard for Privileged Passwordsmakes an SSL connection to SAP HANA using a TCP port between 30015 and 39915, depending on the SAP system number (also known as the "instance number"). For more information, see Safeguard ports.

To configure SAP HANA for Safeguard for Privileged Passwords

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

    This service account must have permissions for remote connections and permissions to change passwords. Consult your SAP security guide for the appropriate settings for your organization.

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

    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 Hana asset type using password authentication. You must specify the SAP HANA Service Name as well as the Port used by the SAP instance.

    When you create an account of Dialog User or Communication Data type, Safeguard for Privileged Passwords 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 for Privileged Passwords will fail.

Preparing SAP Netweaver Application Servers

Safeguard for Privileged Passwordsmakes 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). You can have multiple instances of SAP running on a server, each using a different network port in the range of 3300-3399. The last two digits of the port are called the system number (or instance number). For more information, see Safeguard ports.

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.

If a privileged user for the asset is of System or Communication User 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.

    This service account must have permissions for remote connections and permissions to change passwords. Settings may include:

    • Cross-application Authorization Objects set to Authorization Check for RCF Access
    • Basis: Administration set to User Master Maintenance: User Groups including Change and Lock

    The S_A.SYSTEM authorization profile 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.

    In SAP, when you create a new account of System or Communication User Type, you will be prompted to set a new password.

  3. In Safeguard for Privileged Passwords, create the asset and accounts for the SAP Hana asset type using password authentication. You must specify the SAP HANA Service Name as well as the Port used by the SAP instance.

    When you create an account of System or Communication User 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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级