CASE-SENSITIVE DN causes partial synchronization of LDAP membership.

Problem

If there exist a directory in LDAP with same tree structure differing only in case and sometimes with blank spaces, then there will be partial importation of entries during synchronization. Here is a scenario to depict:

2012-01-27 12:00:00,100 DEBUG [QuartzScheduler_Worker-7] [atlassian.crowd.directory.SpringLDAPConnector] findEntityByDN Entity DN <uid=User1,ou=People,o=sevenSeas,dc=Example,dc=Com> is outside the entity base DN subtree scope <uid=user1,ou=people,o=sevenseas,dc=example,dc=com>

1. For example a tree with the following structure results in a situation where user1,user2 and user3 will be synchronized succesfully which is perfect:

   cn=user1,ou=people,o=sevenSeas,dc=example,dc=com
   cn=user2,ou=people,o=sevenSeas,dc=example,dc=com
   cn=user3, ou=people,o=sevenSeas, dc=example, dc=com
   

2. If the subtree differes a little bit and the base DN is defined as ou=people,o=sevenSeas,dc=example,dc=com, then only user1 and user2 will be synchronized

   cn=user1,ou=people,o=sevenSeas,dc=example,dc=com
   cn=user2,ou=people,o=sevenSeas,dc=example,dc=com
   cn=user3,ou=PEOPLE,o=sevenSeas,dc=example,dc=com
   

Update

There is a patch available for 3.5.17!

1. Download the patch attached to this issue.
2. Replace the JAR file by the same name in <confluence-install>confluence/WEB-INF/lib.
3. Restart Confluence.