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
- Audit
- Automation Suite Robots
- About Automation Suite Robots
- Regenerating Client Secrets
- Frequently Asked Questions
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Last updated Dec 5, 2025
When using client credentials to connect your Automation Suite robots to Orchestrator, the Automation Suite Robots machine template generates a client ID and client secret pair that authorizes the connection between that host machine and Orchestrator. If you feel that the secret key has been compromised, you can regenerate the client secret:
- Go to Tenant > Machines.
-
At the right of the row for the Automation Suite Robot machine template,
select More Actions
and select Edit Machine.
- On the Edit Machine page, in the Client secrets section at the bottom, select Regenerate.
