- 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
- 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
Credential Stores
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, AWS Secrets Manager, and CyberArk. It also provides the necessary architecture to add and manage third party secure stores, if desired.
Beyond the secure stores with built-in support, Orchestrator architecture supports the functionality of loading third-party or developing custom plugins, enabling you to use any desired credential store.
Development documentation for creating your own secure store plugins is available in the UiPath® repository.
Also available there are three samples to assist in your development:
- RandomPass - a read-only store that will generate a random password;
- SQLPass - a read/write store using an external SQL database other than the Orchestrator database;
- Key Vault - the fully functional Key Vault plugin available with your Orchestrator instance.