By: Nikhil Jaisawal user 31 Mar 2020 at 3:01 a.m. CDT

4 Responses
Nikhil Jaisawal gravatar
Hi, I have recently installed gluu on CentOS vm. I have configured below parameters to in cache refresh to sync with my Active Directory. Name: Source Bind DN: cn=<username> max connection: 2 Server:Port: IP:Port Base DN: dc=xx,dc=com Once i click on Test Connection i am getting a error message: **Failed to connect to LDAP server.** Also i have checked the logs from oxauth_persistance.log ``` 2020-03-29 06:48:53,870 INFO [oxAuthScheduler_Worker-3] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] ( - Attempting to create connection pool: 1 2020-03-29 06:48:54,045 INFO [oxAuthScheduler_Worker-3] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] ( - Attempting to create connection pool: 1 2020-03-29 06:48:54,256 INFO [oxAuthScheduler_Worker-3] [org.gluu.persist.ldap.impl.LdapEntryManagerFactory] ( - Created LdapEntryManager: org.gluu.persist.ldap.operation.impl.LdapOperationsServiceImpl@4febaf36 ``` Any help would be appreciated.

By Mohib Zico staff 31 Mar 2020 at 9:26 a.m. CDT

Mohib Zico gravatar
Hello Nikhil, >> Once i click on Test Connection i am getting a error message: Failed to connect to LDAP server. Clearly your Gluu Server VM can't connect to backend LDAP server. There might be couple of reasons: - Parameters which you are using is not correct ( slight syntax error somewhere ) - Network issue between your Gluu Server and LDAP server.

By Nikhil Jaisawal user 01 Apr 2020 at 6:43 a.m. CDT

Nikhil Jaisawal gravatar
Dear @Mohib.Zico, Thanks for the reply. I have verified the both reasons highlighted by you. Parameters are correct and i can reach AD port from gluu server. Please find the below screenshots of my cache refresh configuration. Please let know if there is any issue in configuration.

By Mohib Zico staff 08 Apr 2020 at 11:50 a.m. CDT

Mohib Zico gravatar
I see... You are in 4.1, right?

By Sravana Lakshmi user 14 May 2020 at 1:19 p.m. CDT

Sravana Lakshmi gravatar
Same issue here with 4.1 docker base setup. To check the validity of Parameters and network status, I have created separate docker-openldap(refer: server and tested Multi master replication where ldap search will be performed between docker containers(Add a new user "billy" on the first ldap server and Search on the second ldap server, and billy should show up!). But the same is not working with cache refresh setup as the test ldap server is always showing **Failed to connect to LDAP server**. Is it a bug or am I missing any thing here? Below is the /opt/gluu/jetty/identity/logs/oxtrust_persistence.log 2020-05-14 18:43:50,243 INFO [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] ( - Attempting to create connection pool: 1 2020-05-14 18:44:36,863 INFO [qtp1818402158-10] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] ( - Attempting to create connection pool: 1 2020-05-14 18:45:35,246 ERROR [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] ( - Failed to create connection pool with properties: {bindDN=cn=admin,dc=example,dc=org, useSSL=false, bindPassword=REDACTED,} com.unboundid.ldap.sdk.LDAPException: An error occurred while attempting to connect to server IOException(LDAPException(resultCode=91 (connect error), errorMessage='Unable to establish a connection to server within the configured timeout of 100000 milliseconds.', ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb)) at com.unboundid.ldap.sdk.LDAPConnection.connect( ~[unboundid-ldapsdk-4.0.14.jar:4.0.14]