orchestrator
2023.4
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
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- 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
- Orchestrator testing
- Integrations
- Classic Robots
- Troubleshooting
Orchestrator user guide
Last updated Jul 1, 2025
Note: Before performing the following procedure, make sure you have configured your HashiCorp Vault (read-only) integration.
When storing an asset of type
Credential in a read-only credential store, you must create the secret in Vault and make sure you meet the following requirements:
- the path of the secret must contain the data path configured for the credential store, concatenated with the External Name
configured for that value (if using values per robot) or the asset name otherwise. For example, if the data path is
applications/orchestrator/assets, and the External Name isSAPCredentials, then the secret's path must beapplications/orchestrator/assets/SAPCredentials. -
inside the secret, you must have:
- a key named
Username, with the value containing the username of the credentials. - a key named
Password, with the value containing the password of the credentials.
- a key named
Important: The
Username and
Password fields are case sensitive.
