Custom secrets mapping
- Updated: 2024/10/08
Custom secrets mapping
When using Automation Anywhere with the supported external key vaults the existing work flow enforces a specific Automation 360 encoding format: autologin_<bot-runner_username>, which corresponds to the Control Room username format.
Although, you can continue to use Automation 360 external key vault naming convention specified in the External key vault naming conventions section, you now have the flexibility of using this custom naming format.
The custom secrets naming now allows you to provide your own secret naming format. You can create a mapping of the Control Room username with the secret names. To map the Control Room usernames with the secret names, you must import a .CSV template file which contains the username, secrets names mapping entries into the Control Room.
Prerequisites
Procedure
To import the .CSV template for custom secrets mapping, follow these steps:
- 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 it 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.