By: Prabhu R user 18 Jun 2015 at 7:38 a.m. CDT

5 Responses
Prabhu R gravatar
We tried to connect to our organization LDAP using "Cache Refresh". We configured as per the steps and let it run for the pooling interval. On the pooling time, we get error as, 2015-06-18 12:35:36,266 DEBUG [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-1) Starting conditions aren't reached 2015-06-18 12:35:36,266 DEBUG [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-1) Allowing to run new process exclusively 2015-06-18 12:36:36,500 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-8) **Failed to connect to LDAP server using configuration InumDB** 2015-06-18 12:36:36,500 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-8) Skipping cache refresh due to invalid server configuration 2015-06-18 12:36:36,583 DEBUG [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-8) Allowing to run new process exclusively Our InumDB configuration, ldap.conf.InumDB.bindDN=cn=directory manager ldap.conf.InumDB.bindPassword={bind password} ldap.conf.InumDB.servers=xxx.xxx.xx.xxx:1636 ldap.conf.InumDB.maxconnections=100 ldap.conf.InumDB.useSSL=true ldap.conf.InumDB.baseDNs=ou=people\,o=gluu

By Mohib Zico staff 18 Jun 2015 at 8:44 a.m. CDT

Mohib Zico gravatar
baseDN should be=ou=people\,o=site. Ref doc: * http://ox.gluu.org/doku.php?id=oxtrust:cache_refresh * http://www.gluu.org/docs/admin-guide/configuration/#inum-ldap-server

By Prabhu R user 19 Jun 2015 at 1:41 a.m. CDT

Prabhu R gravatar
We found that bind password was wrong in our configuration and changed it. Now, on pooling time, cache refresh triggered and users from source LDAP has been added to our gluu LDAP. But it throws below error in **oxtrust_cache_refresh.log** 2015-06-19 04:54:42,144 ERROR [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] (pool-5-thread-9) Failed to 'add' person '@!36A3.B263.FC4E.2FD7!0001!DE34.B808!0000!CA94.BEDB' org.gluu.site.ldap.persistence.exception.EntryPersistenceException: Failed to persist entry: inum=@!36A3.B263.FC4E.2FD7!0001!DE34.B808!0000!CA94.BEDB,ou=people,o=@!36A3.B263.FC4E.2FD7!0001!DE34.B808,o=gluu at org.gluu.site.ldap.persistence.LdapEntryManager.persist(LdapEntryManager.java:94) **Cause** Caused by: Connection exception (LDAP config error: schema violation contact LDAP admin.: Entry inum=@!36A3.B263.FC4E.2FD7!0001!DE34.B808!0000!CA94.BEDB,ou=people,o=@!36A3.B263.FC4E.2FD7!0001!DE34.B808,o=gluu violates the Directory Server schema configuration because it is missing attribute cn which is required by objectclass person) at org.gluu.site.ldap.OperationsFacade.addEntry(OperationsFacade.java:305) Also, in **Manage People** menu option in oxTrust GUI, we don't find any users on search.

By Mohib Zico staff 19 Jun 2015 at 3:51 a.m. CDT

Mohib Zico gravatar
`Cause` is showing the clear reason, isn't it?

By Prabhu R user 19 Jun 2015 at 4:44 a.m. CDT

Prabhu R gravatar
No..

By Mohib Zico staff 19 Jun 2015 at 7:12 a.m. CDT

Mohib Zico gravatar
Yes it is. You need to read the log for the solution. The translation of below log message is: *Attribute CN is missing from user* >> inum=@!36A3.B263.FC4E.2FD7!0001!DE34.B808!0000!CA94.BEDB,ou=people,o=@!36A3.B263.FC4E.2FD7!0001!DE34.B808,o=gluu violates the Directory Server schema configuration because it is missing attribute cn which is required by objectclass person)