- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Configuring credential stores
Configure secure credential stores including Azure Key Vault, HashiCorp Vault, and AWS Secrets Manager in Orchestrator.
The following secure stores are already available in Orchestrator:
- Azure Key Vault
- CyberArk CCP
- HashiCorp Vault
- Thycotic Secret Server
- BeyondTrust
- AWS Secrets Manager
Any credential store plugin you choose to use must be Linux-compatible.
To disable the default plugins, set the Plugins.SecureStores.Default key as an empty string in the appsettings.json file. For details, refer to Configuring appSettings.
Uploading custom secure store plugins
If you want to add custom secure store assemblies, you can do so via the uipathctl command line tool, using the uipathctl config orchestrator upload command:
uipathctl config orchestrator upload --securestore-plugins-directory /path/to/plugins/directory
uipathctl config orchestrator upload --securestore-plugins-directory /path/to/plugins/directory
Plugin settings are configured in appSettings using the convention for configuration keys. For details, refer to Configuring appSettings.
Plugins must not write to any storage apart from /tmp.
If you use an external storage configuration at the cluster level, you must indicate this by including the --is-external-storage parameter.
-
Add the custom secure store plugins of your choice to
appSettingsusing the following command:Plugins.SecureStores.<<FriendlyName>>.<<SettingName>>Plugins.SecureStores.<<FriendlyName>>.<<SettingName>> -
Enable the custom secure store plugins by updating
appSettingswith the relative path of the plugin (from thesecurestorepluginsfolder):"Plugins.SecureStores":"myplugin/MyPlugin.dll,secondPlugin/SecondPlugin.dll""Plugins.SecureStores":"myplugin/MyPlugin.dll,secondPlugin/SecondPlugin.dll"