- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
A credential store is a named location within a secure store, such as CyberArk, from which you can store and retrieve sensitive data such as Robot credentials and credential assets when needed. Orchestrator supports the use of multiple credential stores at tenant level, and provides built-in support for Azure Key Vault, CyberArk CCP, HashiCorp Vault, Thycotic Secret Server, BeyondTrust, and AWS Secrets Manager. It also provides the necessary architecture to add and manage third party secure stores, if desired.
The Credentials page is split in two views: Stores and Proxies.
- The Stores page allows you to create new stores, view existing stores and their properties, and delete any current credential store. Note that the native Orchestrator Database store is automatically created, will always appear first in this list and be the Default store for all new tenants.
The Proxies page allows you to create new proxies for your own custom credential stores, view a list of existing proxies, edit, and remove them.