orchestrator
2023.10
true
- 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
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Oct 17, 2024
Storing Assets in Azure Key Vault (read only)
When storing an asset of type credential 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 value if using values per robot or the asset name otherwise. Note that Azure Key Vault secret names must
be a 1-127 character string, starting with a letter and containing only
0-9,a-z,A-Z, and-. For more details, see the Azure Key Vault documentation - the secret value must be a
.jsonstring with the format{"Username": "user", "Password": "pass"}.
