Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

One Identity Safeguard for Privileged Passwords 7.4.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 page Privileged access requests Appliance Management
Appliance Backup and Retention Certificates Cluster Global 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 Importing objects
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

Preparing Sybase (Adaptive Server Enterprise) servers

To prepare a Sybase ASE (Adaptive Server Enterprise) server for SPP, refer to the documentation for your Sybase ASE server for information about how to setup and secure encryption. Make sure the service account you use has the sso_role assigned.

To enable SSL server certificate validation, add the server’s signing authority certificate to the Trusted Certificates store in SPP. For more information, see Trusted CA Certificates..

For more information about how SPP database servers use SSL, see How do SPP database servers use SSL.

Preparing SonicOS devices

SPPsupports SonicOS Internet appliances. SPP uses the SSH protocol to connect to SonicOS devices.

To prepare a SonicOS device for SPP

  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: SPP 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 SPP using password authentication.

Preparing SonicWALL SMA or CMS appliances

Here are some important notes about configuring a SonicWALL SMA or CMS appliance for SPP:

  1. Use the local admin account as the service account.
  2. SPP can only manage the admin account; it cannot manage other local accounts or accounts from external providers.

Preparing SQL Servers

To prepare a MicrosoftSQL Server for SPP, refer to the documentation for your SQL server for information about how to set up and secure encryption.

To enable SSL server certificate validation, add the server’s signing authority certificate to the Trusted Certificates store in SPP. For more information, see Trusted CA Certificates..

For more information about how SPP database servers use SSL, see How do SPP database servers use SSL.

To configure a SQL Server for SPP (with an authentication type of Local System Account)

NOTE: To manage a Microsoft SQL server asset with the authentication type of Local System Account, you need a local Windows account that is a Security Admin in SQL. In order to use this authentication type, you must add a Windows asset and an SQL Server asset to SPP.

  1. Log in to the SPP client as an Asset Administrator.
  2. Navigate to Asset Management > Assets.
  3. Add a Windows asset that matches the OS of the server that is hosting the SQL database.
    1. On the Connection tab:
      • Authentication Type: Set to Password.
      • Service Account: Set to a local user that is a member of the Administrator's group.
    2. Add other accounts as needed.

    Save the asset.

  4. Add an SQL Server asset.
    1. On the Connection tab:

      • Authentication Type: Set to Local System Account.
      • 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.

      • Run Test Connection and verify the connection works.

    Save the asset.

To configure a SQL Server for SPP (with an authentication type of Directory Account)

NOTE: To manage a Microsoft SQL asset with the authentication type of Directory Account, you need a domain account that is a Security Admin in SQL. In order to use this authentication type, you must add a directory and directory users to SPP.

  1. Add a directory and directory users.
    1. Log in as an Asset Administrator.
    2. Navigate to Asset Management > Assets to add a directory for your domain.
    3. Once added, select the domain and open the Accounts tab to add domain user accounts. For more information, see Adding an account to an asset..
  2. Add an SQL Server asset and account information.
    1. Log in to the SPP client as an Asset Administrator.
    2. From Asset Management > Assets, add an SQL Server asset.
    3. On the Connection tab, complete the following:

      • Authentication Type: Set to Directory Account.
      • 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.

      • Run Test Connection and verify the connection works.
  3. Save the asset.

To configure a SQL Server for SPP (with an authentication type of Password)

NOTE: To manage a Microsoft SQL server asset with the authentication type of Password, you need a local database account that is a Security Admin in SQL.

  1. Log in to the SPP client as an Asset Administrator.
  2. Navigate to Asset Management > Assets.
  3. Add an SQL Server asset.
    1. On the Connection tab:

      • Authentication Type: Set to Password.
      • Account Name: Enter the account name.

      • Run Test Connection and verify the connection works.

  4. Save the asset.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating