Custom platforms
desktop client only
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.
Create and manage custom platforms in Administrative Tools | Settings | Asset Management | Custom Platforms.
The Custom Platform pane displays the following.
Table 128: Custom platform: Properties
Name |
The name of the platform type which may be a product name. |
Version |
The version of the target platform to use as an identifier. |
Architecture |
The CPU architecture to use as an identifier. If not applicable, use Any. |
Platform Script |
The name of the custom platform script file displays once selected. |
Allow Sessions Requests |
If selected, session access requests are allowed. |
Use the following toolbar buttons to manage the custom platform settings.
Table 129: Custom Platform: Toolbar
Add |
Add a custom platform. For more information, see Adding a custom platform. |
Delete Selected |
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. | |
Refresh |
Update the list of custom platforms. |
View
|
View the custom platform script parameters including:
- Supported operations, for example Suspend and Restore Accounts, Check System, Check Password, Change Password
- Details including Name, Task, Type, Default, and Description
|
Download Selected Script |
Download the selected custom platform JSON script. |
Creating a custom platform script
desktop client only
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
desktop client only
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
- Have the custom platform script file available to upload.
- Navigate to
Administrative Tools | Settings | Asset Management | Custom Platforms.
- Click
Add.
- These fields display:
- Name: Enter the unique name of the platform type, which may be a product name.
- Version: Enter the version of the target platform to use as an identifier.
- Architecture: Enter the CPU architecture to use as an identifier. If not applicable, use Any.
-
Platform Script: Click Browse. Navigate to and select the script file. Click Open. The selected custom platform script file displays.
- 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.
- Click OK. If the custom platform script has errors, an error message like the following displays: Definition was not a valid json object .
Tags
desktop client only
Asset Administrators can define rules that will dynamically add tags to assets and asset accounts so that they can be easily identified and added to dynamic groups. Use the Administrative Tools | Settings | Asset Management | Tags pane to create and manage dynamic tags for assets and asset accounts.
In addition, Asset Administrators can manually add static tags to assets and accounts on the General tab of the Assets or Accounts view. For more information, see Manually adding a tag to an asset and Manually adding a tag to an account.
The Tags pane provides a centralized view of all the tags defined for assets and asset accounts, regardless of how they were assigned. It displays the following details.
Table 130: Tags: Properties
Name |
The name assigned to the tag when it was created. |
Asset Partition |
The asset partition to which the tag belongs. |
Rules |
Indicates whether there is a rule associated with the selected tag. A check mark in this column indicates that the tag has an asset or asset account rule. |
Description |
Information about the tag. |
Use these toolbar buttons to manage tags.
Related Topics
When does the rules engine run for dynamic grouping and tagging