LDAP delta synchronisation fails

Agnes Schürmann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 15, 2012

When creating a new connection to an LDAP (ADAM) (see attachment) only the first synchronisation works.

After that, there is always the following error:

2012-08-16 08:55:18,062 INFO http-8080-41 embedded.admin.list.DirectoriesController sync User directory synchronisation requested: Active Directory server , type: CONNECTOR

2012-08-16 08:55:18,078 INFO QuartzScheduler_Worker-7 atlassian.crowd.directory.DbCachingRemoteDirectory synchroniseCache synchronisation for directory 56688641 starting

2012-08-16 08:55:18,375 FATAL QuartzScheduler_Worker-7 springframework.ldap.control.AbstractRequestControlDirContextProcessor postProcess No matching response control found for paged results - looking for 'class javax.naming.ldap.PagedResultsResponseControl

2012-08-16 08:55:18,375 INFO QuartzScheduler_Worker-7 atlassian.crowd.directory.DbCachingRemoteDirectory synchroniseCache delta synchronisation complete in 297ms

2012-08-16 08:55:18,390 ERROR QuartzScheduler_Worker-7 atlassian.crowd.directory.DbCachingDirectoryPoller pollChanges Error occurred while refreshing the cache for directory 56688641 .

com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.InvalidNameException: CN=Deleted Objects,null: LDAP: error code 34 - 0000208F: NameErr: DSID-031001BF, problem 2006 (BAD_NAME), data 8350, best match of:

'CN=Deleted Objects,null'

; nested exception is javax.naming.InvalidNameException: CN=Deleted Objects,null: LDAP: error code 34 - 0000208F: NameErr: DSID-031001BF, problem 2006 (BAD_NAME), data 8350, best match of:

'CN=Deleted Objects,null'

; remaining name 'CN=Deleted Objects,null'

at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:333)

at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:366)

at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findTombstonesSince(MicrosoftActiveDirectory.java:368)

at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findUserTombstonesSince(MicrosoftActiveDirectory.java:309)

at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseUserChanges(UsnChangedCacheRefresher.java:308)

at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseChanges(UsnChangedCacheRefresher.java:161)

at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:610)

at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63)

at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)

at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29)

at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)

at org.quartz.core.JobRunShell.run(JobRunShell.java:199)

at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$1.run(ConfluenceQuartzThreadPool.java:14)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)

Caused by: org.springframework.ldap.InvalidNameException: CN=Deleted Objects,null: LDAP: error code 34 - 0000208F: NameErr: DSID-031001BF, problem 2006 (BAD_NAME), data 8350, best match of:

'CN=Deleted Objects,null'

; nested exception is javax.naming.InvalidNameException: CN=Deleted Objects,null: LDAP: error code 34 - 0000208F: NameErr: DSID-031001BF, problem 2006 (BAD_NAME), data 8350, best match of:

'CN=Deleted Objects,null'

; remaining name 'CN=Deleted Objects,null'

at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:126)

at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:319)

at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:237)

at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:300)

... 13 more

Caused by: javax.naming.InvalidNameException: CN=Deleted Objects,null: LDAP: error code 34 - 0000208F: NameErr: DSID-031001BF, problem 2006 (BAD_NAME), data 8350, best match of:

'CN=Deleted Objects,null'

; remaining name 'CN=Deleted Objects,null'

at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3005)

at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2820)

at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1829)

at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1752)

at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)

at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)

at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:257)

at sun.reflect.GeneratedMethodAccessor357.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.springframework.ldap.transaction.compensating.manager.TransactionAwareDirContextInvocationHandler.invoke(TransactionAwareDirContextInvocationHandler.java:92)

at $Proxy689.search(Unknown Source)

at org.springframework.ldap.core.LdapTemplate$3.executeSearch(LdapTemplate.java:231)

at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:293)

... 15 more

We have new Users every day and it is a major problem for us.

Thanks for your advice

3 answers

0 votes
Amit Girme July 11, 2013
Temporary solution is remove incremental synchronization check box. Atlassian working on it https://jira.atlassian.com/browse/CWD-2581 Hopefully it wont take long.
0 votes
Tobias Anstett _K15t_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 3, 2012

Hi Agnes,

Have you already solved the issue? I have the same problem, but in contrast to the solution proposed before my user has all required permissions set.

For me it looks like the distinguished name is not correctly created by Confluence.

Caused by: javax.naming.InvalidNameException: CN=Deleted Objects,null: [LDAP: error code 34 - 0000208F: NameErr: DSID-031001F7, problem 2006 (BAD_NAME), data 8350, best match of:
	'CN=Deleted Objects,null'
]; remaining name 'CN=Deleted Objects,null'

Actually the name should be 'CN=Deleted Objects,OU=Test,DC=domain,DC=com' instead of 'CN=Deleted Objects,null' - of course OU and DC are just example values.

Cheers,
Tobias

0 votes
Andrew Frayling
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 15, 2012

Hi Agnes,

It looks like you're hitting point 5 as documented at https://confluence.atlassian.com/display/JIRA/User+Management+Limitations+and+Recommendations#UserManagementLimitationsandRecommendations-SpecificNotesforConnectingtoActiveDirectory

You either need to bind to LDAP as an admin user or change the permissions on the Deleted Objects container so that the user Confluence is binding as has permissions to access Deleted Objects - http://support.microsoft.com/kb/892806

Hope that helps?

Andrew.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events