Troubleshooting LDAP timeout error during Active Directory role mapping
- Updated: 2025/03/17
Troubleshooting LDAP timeout error during Active Directory role mapping
To troubleshoot LDAP timeout errors during Active Directory role mapping in Automation 360, update the um.properties file with settings for LDAP search retries, connection pool enablement, and connection pool timeout. This improves LDAP connection handling and resolves timeout issues.
If the Active Directory sync process is taking longer and the action is causing timeout issues when connecting to the LDAP server a retry mechanism has been implemented. If a timeout occurs, a new connection is created and used for retries. By default, the retry happens 3 times, but the number of retries is now configurable through parameters in the um.properties file, allowing users to retry more than 3 times if needed.
Follow the procedure to configure additional parameters in um.properties file:
- Go to the Control Room installation path.
- From the list of files in the config folder, open the
um.properties file with an XML editor and update the
following default settings to troubleshoot the Active Directoryrole
mapping timeout error. In case you want to make changes to the default values, you
can add them in the um.properties file with the new values:
- Edit the value
3
to the number of retries you prefer. For example, to set the retries to 5, edit the um.ldap.search.user.retries as following:um.ldap.search.user.retries=5
- Enable LDAP connection pool by specifying
true
instead of the default value offalse
by editing the um.jndi.ldap.connect.pool parameter:um.jndi.ldap.connect.pool=true
- Combined with the setting, you must also edit the default connect pool
timeout value from
300000
to timeout value of your choice. For example, to set the timeout value to500000
, edit the um.jndi.ldap.connect.pool.timeout as following:um.jndi.ldap.connect.pool.timeout=500000
This sets the connect pool timeout to 5,000,00 milliseconds.
Note: If the timeout issue persists after applying the above changes, submit a support ticket to Automation Anywhere for further assistance. - Edit the value