Automation 360 supports two models of object naming conventions.
- Secrets naming convention: This is the legacy and default naming convention. For the external key vaults, agent auto-login credentials must adhere to the required naming conventions. For more information, see Secrets naming convention.
- Custom secrets naming convention: This naming convention allows you to provide your own secret naming format without conforming to any Automation 360 encoding conventions. For more information, see Custom secrets naming convention.
The following table lists the credential retrieval use cases along with the supported naming convention model.
| Use case | Secrets naming convention (old) | Custom secrets naming convention (New) | Supported deployment |
|---|---|---|---|
| Agent auto-login: Agent auto-login naming conventions | Yes. For more information, see Secrets naming convention. | Yes. For more information, see Custom secrets naming convention. | On-Premises and Cloud |
| Agent automation: Agent automation naming conventions | Yes. For more information, see Secrets naming convention. | Not applicable | On-Premises and Cloud |
| Control Room bootstrap: | Yes. For more information, see Secrets naming convention. | Not applicable | On-Premises only |
| Control Room system credentials: | Yes. For more information, see Secrets naming convention. | Yes. For more information, see Custom secrets naming convention. | On-Premises only |
Note: For BeyondTrust Password Safe and ARCON Key Vault, only
agent auto-login use case is supported.