Unable to log in to Orchestrator using SSO, the Orchestrator URL is loading fine, but when clicking on the SSO login option, it does not load the tenant and gives 504 error.
Issue Description
In a standalone UiPath Orchestrator deployment integrated with Active Directory (AD), users were unable to log in using Windows AD credentials, while local Orchestrator users could authenticate successfully.
This indicated that the issue was isolated to the Active Directory authentication flow via the Identity Server.
Logging into Orchestrator using Windows AD credentials fails with 504 Gateway Timeout.
Local admin login works successfully.
The Active Directory user list in Manage Access fails to load user profiles.
The system is unable to complete authentication queries against AD.
Steps to Resolve:
-
Validate LDAP connectivity
-
Confirm access to the AD Domain Controller over port 389.
-
-
Enable/restore port access
-
Update firewall/network rules to allow:
-
TCP 389
-
UDP 389 (recommended)
-
-
Source: Orchestrator/Identity Server host
-
Destination: Domain Controller(s)
-
-
Restart identity services
-
Restart the UiPath Orchestrator site/services after port access is restored.
-
-
Verify
-
Log in with AD credentials
-
Confirm user list loading in "Manage Access"
-
Confirm no new timeout errors in logs
-
Conclusion
The 504 Gateway Timeout occurred because Identity Server could not communicate with the Domain Controller due to blocked LDAP port 389.
Once port 389 access was restored, AD login and profile loading worked as expected, and all timeout errors were resolved.