orchestrator
latest
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
- Configuring automation capabilities
- Solutions
- Audit
- Integrating credential stores
- Managing credential stores
- The Orchestrator Credentials Proxy
- Managing credential proxies
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
The Orchestrator Credentials Proxy

Orchestrator user guide
Last updated Apr 1, 2025
- Known issue
- Installation
- Hardware and software requirements
- Through the .msi installer
- Through the Docker image
- Configuration
- Connected and Disconnected proxy
- CyberArk
- CyberArkCCP
- HashiCorp Vault
- HashiCorp Vault (read only)
- Disconnected proxy-only
- Configuration samples
- Validation
- Logging
- Security considerations
- Using the Orchestrator Credentials Proxy with a load balancer
- Elements that must remain identical across nodes
- Important things to consider
- Updating the Orchestrator Credentials Proxy certificate