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, then there will be partial importation of entries during synchronization. Here is a scenario to depict:

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
   

Workaround
The workaround at the moment is to enable naive DN matching. This should be fine with memberDNs in compact format. membership can still be broken if memberDNs are not in compact view.