Chat now with support
Chat mit Support

One Identity Safeguard for Privileged Passwords 7.0.2 LTS - 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

Adding a registered connector

It is the responsibility of the Asset Administrator to configure registered connectors.

To add a registered connector

IMPORTANT: Before adding a registered connector, read the Starling Connect documentation for instructions on configuring the connector within Starling Connect for use with Safeguard for Privileged Passwords. The connectors currently available for use with Safeguard for Privileged Passwords are listed in the Starling Connect documentation.

  1. Navigate to:

    • web client: Asset Management > Connect and Platforms > Registered Connectors.

  2. Click  Add.
  3. These fields display:
    1. Registered Connectors: Select the connector (already configured in Starling Connect) to register with Safeguard for Privileged Passwords.
    2. Starling Connector Version: Select the version for the Starling connector.
    3. Display: Enter a display name for the connector.
    4. Visible To All Partitions: Select this check box to make the registered connector visible to all partitions.
    5. Visible To Partitions: Available when Visible To All Partitions is not selected, use this section to define which partitions this registered connector will be visible to:
      • (Add): Use this button to add a new partition.
      • (Remove): Use this button to remove a previously selected partition.

  4. To add the registered connector, click OK.

    The connector will now be registered as a platform and be available as a platform type in the definition of an asset.

IMPORTANT: When using a registered connector with Safeguard for Privileged Passwords, there may be additional considerations involved when configuring certain functionalities. For example, Azure AD uses throttling to limit the number of password changes that can occur within a set period of time. This can mean errors are reported within Safeguard for Privileged Passwords when a large number of accounts associated with a registered Azure AD connector are all scheduled to automatically update their passwords due to their password management settings.

Custom platforms

The Asset Administrator adds a custom platform that includes uploading the custom platform script with the platform's commands and details. Auditors and Partition Administrators have read only rights. Custom platforms are global across all partitions. The custom platform can be selected when adding or updating an asset.

Navigate to:

  • web client: Asset Management > Connect and Platforms > Custom Platforms.

Use the following toolbar buttons to manage the custom platform settings.

Table 169: Custom Platforms: Toolbar
Option Description
Add

Add a custom platform. For more information, see Adding a custom platform.

Delete

Remove the selected custom platform.

CAUTION: If the custom platform is associated with an asset, deleting the custom platform may halt password or SSH key validation and reset. A warning displays, indicating that the asset will be assigned to the Product platform type Other. Enter Force Delete to confirm the deletion.

Edit

Edit the selected platform.

Download

Download the selected custom platform JSON script.

Refresh

Update the list of custom platforms.

Related Topics

Creating a custom platform script

Adding a custom platform

Creating a custom platform script

A custom platform script identifies the platform's commands and associated details. Scripts are written in JSON. Scripts include metadata, parameters, function blocks, operations, and if/then constructs to authenticate to the platform and perform password or SSH key validation and reset. The custom platform script is uploaded when adding the custom platform.

An Asset Administrator can create an asset and accept default values in the associated custom script. If you later upload a new version of the custom platform script with different defaults, the asset defaults are not changed.

A delegated administrator cannot create a custom platform script.

Sample scripts

Sample custom platform scripts and command details are available at the following links available from the on GitHub:

CAUTION: Example scripts are provided for information only. Updates, error checking, and testing are required before using them in production. Safeguard for Privileged Passwords checks to ensure the values match the type of the property that include a string, boolean, integer, or password (which is called secret in the API scripts). Safeguard for Privileged Passwords cannot check the validity or system impact of values entered for custom platforms.

During development, check your JSON using a validator.

Adding a custom platform

It is the responsibility of the Asset Administrator to configure the rules so Safeguard for Privileged Passwords handles custom platforms. The custom platform script must be available for uploading. For more information, see Creating a custom platform script.

To add a custom platform

  1. Have the custom platform script file available to upload.
  2. Navigate to:
    • web client: Asset Management > Connect and Platforms > Custom Platforms.
  3. Click  Add.
  4. These fields display:
    1. Name: Enter the unique name of the platform type, which may be a product name.

    2. Platform Script: Click Browse. Navigate to and select the script file. Click Open. The selected custom platform script file displays.

    3. Select the Allow Sessions Requests check box to allow session access requests. This check box is typically selected for SSH. Clear the Allow Sessions check box to prohibit session access requests.
  5. Click OK. If the custom platform script has errors, an error message like the following displays: Definition was not a valid json object .
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen