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 . It also provides the necessary architecture to add and manage third party secure stores, if desired.

Note: The credential stores feature must be enabled for your tenant by the Orchestrator administrator. See here for details.

Credential store plugins

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.

Loading third-party plugins

1. Navigate to the \Orchestrator\Plugins folder in your Orchestrator installation directory.
2. Save the .dll files of your plugin in this folder.
3. Update the UiPath.Orchestrator.dll.config file with the plugin mentioned in the UiPath.Orchestrator.dll.config guide.
4. Restart your Orchestrator instance and check the logs to confirm the plugin was loaded successfully.
5. Your new credential store should now be available when configuring credential stores.

Developing plugins

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.