orchestrator
2023.10
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Storing Unattended Robot Passwords in Azure Key Vault (read only)
Orchestrator User Guide
Last updated Nov 7, 2024
Storing Unattended Robot Passwords in Azure Key Vault (read only)
When storing an unattended robot password in an Azure Key Vault (read only) credential store, you must create the secret in the Secrets section of the vault, as follows:
- the name of the secret must be the External Name configured for that robot. If you do not enter any external name, the user name field is used instead, with the characters
\
,@
and.
replaced with-
. If the resulting string does not conform to the secret name restrictions of Azure Key Vault, you must provide an External Name. For more details, see Azure Key Vault documentation - the secret value must be the password for the robot.