Custom secrets naming convention
- Updated: 2025/03/17
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. 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.
Note: Ensure that you have the view and manage settings permission
to proceed with the procedure.
Prerequisites
Procedure
To import the Custom Secrets Name Mapping Template.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 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.