Issue #693 has been updated by Clément OUDOT. Status changed from Feedback to Closed % Done changed from 70 to 100
Can't test with spaces in DN. Sync to AD works now without problem. ---------------------------------------- Bug #693: RDN value is forced to lower case when creating an entry http://tools.lsc-project.org/issues/693 Author: Clément OUDOT Status: Closed Priority: Normal Assigned to: Clément OUDOT Category: Core Target version: 2.1 Problem in version: I do not reproduce this behaviour with 2.0, but with 2.1, the DN value is forced to lower case when the entry is created. This raises a bug with AD, as AD copy the RDN value inside the corresponding attribute in the entry. For example entry "cn=Clement OUDOT,ou=users,dc=example,dc=com" is created as: <pre> dn: cn=clement oudot,ou=users,dc=example,dc=com cn: clement oudot </pre> Then, at next LSC run, source cn value (Clement OUDOT) must replace destination value (clement oudot), but as cn is also the RDN, the modify operation is refused. The LSC do not try to launch a MODRDN as LSC knows that DN comparaison is not case sensitive. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
