The Asset Administrator can manually add an API key to an account.
To add an API key
-
Navigate to Asset Management > Accounts.
- In Accounts, select an account from the object list.
- Click (View Details) from the toolbar.
- Navigate to Properties > Secrets.
-
In the API Keys section, click the New API Key button.
-
Depending on the type of account, the following information may be required:
-
Name: Enter the name of the API key. This must match the name used in the platform.
-
Description: Enter a description of the API key.
-
Expires: Enter the number of days before the key will expire.
-
You can also set the API Key to match an existing key for the account. This option does not change the API key information on the platform. This can be done at a later time (using the Set button associated with the API key tile) or a new key will be generated when the key is changed. The following options may appear depending on the type of platform:
- Client Identifier: Copy the client identifier from the platform and add it to this field.
-
Client Secret: Copy the client secret from the platform and add it to the field. Once configured, click Copy to put it into your copy buffer. You can then log in to your device, using the old client secret, and change it to the client secret in your copy buffer.
-
Client Secret Identifier (Azure AD only): Copy the client secret identifier from the platform and add it to the field. If the identifier doesn't match, when you attempt to change the API key for the Azure AD platform it will create a new one with the identifier set in Safeguard for Safeguard for Privileged Passwords.
-
Click Save.
The Asset Administrator can manually check, change, or set an API key associated with Azure AD and AWS connectors.
To manually check, change, or set an API key
NOTE: Should 4 or more API keys be configured, the tiles will be condensed into a single summary tile. To access and manage the individual API keys, click the name of the tile (API Keys <n>). This will open a pane containing a table view of the configured API keys as well as toolbar options for managing the keys.
-
Navigate to Asset Management > Accounts.
- In Accounts, select an account from the object list.
- Click (View Details) from the toolbar.
- Navigate to Properties > Secrets.
-
Each configured API key is represented by a tile available on this page which provides the following options:
-
Set to set the API key secret in the Safeguard for Privileged Passwords database. This option does not change the API key information on the platform. The following options may appear depending on the type of platform:
-
Client Identifier: Copy the client identifier from the platform and add it to this field.
-
Client Secret: Copy the client secret from the platform and add it to the field. Once configured, click Copy to put it into your copy buffer. You can then log in to your device, using the old client secret, and change it to the client secret in your copy buffer.
-
Client Secret Identifier (Azure AD only): Copy the client secret identifier from the platform and add it to the field. If the identifier doesn't match, when you attempt to change the API key for the Azure AD platform it will create a new one with the identifier set in Safeguard for Safeguard for Privileged Passwords.
-
Set Client Secret: Click this button to save the configuration.
-
Check to verify the API key is in sync with the Safeguard for Privileged Passwords database. If the API key verification fails, you can change it.
-
Change to reset and synchronize the API key with the Safeguard for Privileged Passwords database.
-
(Remove): Click this button to remove a previously configured API Key.
The Asset Administrator can access an archive of an account's API Keys.
To access an account's API key archive
- Navigate to Asset Management > Accounts.
- Select an account and click (View Details).
- Navigate to Properties > Secrets.
- For a configured API key, click View Archive.
-
In the API Key archive dialog, select a date. If you select today's date (or a previous date) and no entries are returned, this indicates that the asset is still using the current API key.
-
In the View column, click to display the API Key that was assigned to the asset at that given date and time.
-
In the details dialog, click Copy to copy the API Key to your copy buffer.
Many asset types support the use of a TOTP authenticator for the accounts associated with it using password requests. The following instructions explain how to add a TOTP authenticator to an existing asset.
To set up a TOTP authenticator
-
Navigate to Asset Management > Accounts.
- In Accounts, select an account from the object list.
- Click (View Details) from the toolbar.
- Navigate to Properties > Secrets.
-
On the TOTP Authenticator tile available on this page, click Set.
-
On the Set TOTP Authenticator pane, select one of the following options:
NOTE: Once you start the process for setting up a TOTP authenticator you will need to connect the authenticator with the account in Safeguard for Privileged Passwords by entering the code(s) sent by the authenticator within a set time limit. It is strongly suggested you have your authenticator ready prior to beginning this process to avoid having to restart the setup process due to timing out.
-
QR Code Image: Select this method to connect with the TOTP authenticator through the use of a QR code image file. Click Browse Your Computer to select the QR code image file or drag the QR code image file into the dashed box.
-
URI or Secret String: Select this option to connect with the TOTP authenticator through the use of the URI string or secret generated by the authenticator. If only a secret is provided, then the process for generating the string will depend upon the authenticator itself.
Click Submit.
-
A Setup Confirmation Code section will appear as soon as the authenticator setup begins and you will need to start entering the provided code(s) into your authenticator (you can use the Copy button to copy the code instead of typing the value). The amount of time you have left before the code becomes invalid and a new code is displayed to the right of the Copy button.
The number of code(s) required depends upon the requirements for the authenticator (for example, AWS requires 2 successive codes be entered, with each code being available for approximately 30 seconds. Only 5 codes will be displayed before the authenticator setup times out and you will need to restart the process.). If you are unable to successfully complete the setup, click Remove Authenticator to restart the process.
-
Once you have successfully completed the TOTP authenticator setup, click Done.