The custom secrets naming allows you to provide your own secret naming format without conforming to any Automation 360 encoding conventions.
You can create a mapping of the Control Room username with the secret
names. You can manage these mappings in two ways:
- Single entry: Add, edit, or delete one mapping directly in the custom secrets mapping table, without needing a CSV upload.
- Bulk entries: Import a .CSV template file containing username, secrets names mapping entries into the Control Room. You can also use this method for single-entry updates.
Before you begin
Add, edit, or delete a single mapping entry
To manage an individual mapping entry without a .CSV file, follow these steps:
- Navigate to .
- Click the vertical ellipses (
) icon next to the vault name in the Auto Login Mapping table.
- Click Edit Auto Login (
) option.
- Select Secret mappings.
- Do the following based on your requirement:
To add a new entry
- Click + icon on top of the Secret
mappings table.
- Enter the Username, System
name, and Account name.
- Click Add.Note: The system validates whether the entered username exists in the Control Room. If the username does not exist, an error is displayed and the entry is not saved.
To edit an existing entry
- Click the vertical ellipses (
) icon next to the secret mapping details you want to edit.
- Click Edit mapping (
) option.
- Update the System name or Account
name.
- Click Save.
To delete an entry
- Click the vertical ellipses (
) icon next to the secret mapping details you want to remove.
- Click Delete mapping (
) option.
- Click Delete on a confirmation pop-up.
- Click Delete.
- Click + icon on top of the Secret
mappings table.
Each add, edit, and delete action on a mapping entry is recorded in the audit log. See Custom secret mapping audit entries.
Import the Custom Secrets Name Mapping Template.csv for bulk mapping
Note: In Automation 360 v.41 and
later, you can import the
Custom Secrets Name Mapping Template.csv
template through only one of the following paths, depending on the features enabled
for your environment:- If the option is visible, perform custom secret mapping using this flow. This flow supports configuring auto-login for a selected external vault connection in environments that use one or more external vaults.
- If not, use .
To import the Custom Secrets Name Mapping
Template.csv template for custom secrets mapping, follow these
steps:
- Do one of the following based on the navigation path visible to you:
- Navigate to ManageExternal
VaultAuto Login
- Click Add Auto login, Add or + icon.
- From the Select vault drop-down list, choose one of your vault connections.
- Under Auto login,
Enabled is selected by default. Click
Disabled if you want to disable auto
login for this vault connection.
- Click Next to open the Secret mapping page.
- Navigate to
- Click Edit.
- Select Manage custom secrets mapping.
- Click Edit.
- Navigate to ManageExternal
VaultAuto Login
- Click the CSV file template or Download CSV
file template to download Custom Secrets Name Mapping
Template.csv template.
- Open the downloaded .csv file and add the username, secret name in the format
specified.Note: In the Automation 360 On-Premises deployments with Active Directory, prefix the username with domain. Example: domain\username.
- Click Import .csv and browse to select the
Custom Secrets Name Mapping Template.csv template file
to map the Control Room usernames with the secret names.
The import Import .csv template must follow the specified format. You cannot use the exported mapping entries Import .csv file to import new entries.
- Click Import and save. The custom secrets mapping table is populated with the updated entries.
- Only 100 records can be processed at a time. For additional records, you can repeat the import action multiple times.
- Each username maps to a single secret name. If a matching username is found, the system will overwrite the existing entry. If there are duplicate records, the last processed entry will take priority.
- Multiple users can be mapped to the same secret name.
- The username and secret name fields are required. If either is missing, the entry is considered invalid.
- The system checks if the username exists in the Control Room. If the specified username does not exist, the entry is considered invalid.
- If the system fails to save the mapping, an exception is raised and no records will be processed.