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
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Oct 17, 2024
Storing Unattended Robot Credentials in HashiCorp Vault (read only)
Note: Before performing the following procedure, make sure you have configured your HashiCorp Vault (read-only) integration.
When storing an unattended robot password 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 robot. For example. if the data path is
applications/orchestrator/robots, and the External Name isrobot01, then the secret's path must beapplications/orchestrator/robots/robot01. - inside the secret, you must have a key named
Value, and the value must be this robot's password.
