- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- 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
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Configuring credential stores
Reference for credential store configuration options in Orchestrator, including supported secure store plugins in Automation Suite on EKS/AKS.
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"