automation-suite
2024.10
false
- 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 creation
- 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
- After Disaster Recovery Dapr is not working properly for Task Mining
- Task Mining initialization issue in Kerberos
Automation Suite on EKS/AKS installation guide
Last updated Mar 31, 2026
Task Mining initialization issue in Kerberos
Description
The Task Mining service may fail to initialize in Kerberos environments due to:
- A missing
kerberos-discoverygroup-user-keytabsecret. - The
discoverygroupapp not being included in theenabledAppsparameter of theIntegratedAuthapp.
Solution
To address the issue, take the following steps:
- Create the missing
kerberos-discoverygroup-user-keytabsecret. You can duplicate an existing keytab secret and name the new one askerberos-discoverygroup-user-keytab. - Add
discoverygroupto theenabledAppsparameter in theIntegratedAuthapp configuration.
Once you make these changes, restart the relevant services and confirm that Task Mining initializes successfully.