automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- Step 1: Removing old cache keys
- Step 2: Updating AD integration and authentication
- Step 3: Validating the Insights migration
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
Automation Suite on EKS/AKS installation guide
Last updated May 6, 2025
Step 2: Updating AD integration and authentication
To configure AD integration, refer to Configuring SSO: Active Directory.
If AD integration and authentication were enabled in the standalone deployment, take the following steps in the Automation Suite cluster:
- Make sure the domain controllers are discoverable by the Automation Suite cluster. If not, use the Kube DNS configuration;
- Configure integrated Windows authentication and Kerberos authentication using keytab file;
- Configure LDAP integration via the Portal under the host admin;
- Configure Windows authentication via the Portal under the host admin;
-
Configure LDAPS for secure connection to LDAP.
Note: The account used for the LDAP integration configuration should only have read access to all trusted domains in the current and trusted forests.
