- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
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, provides built-in support for Azure Key Vault, CyberArk CCP, HashiCorp Vault, and BeyondTrust, CyberArk, and the architecture enabling you to develop a plugin for other secure stores, if desired.
This Credential Stores page enables 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 and will always appear first on this list and be the Default store for all new tenants.
The credential stores feature must be enabled for your tenant by the Orchestrator administrator.
See here for details.
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.
- Navigate to the
\Orchestrator\Pluginsfolder in your Orchestrator installation directory. - Save the
.dllfiles of your plugin in this folder. - Update the
UiPath.Orchestrator.dll.configfile with this plugin as detailed here. - Restart your Orchestrator instance and check the logs to confirm that the plugin was loaded successfully.
- Your new credential store should now be available when creating a new 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.
