Issue #264 has been updated by Jonathan Clarke. Subject changed from Not proper evaluation for create (and probably delete) when base.dn is not rewrited to Operation choice may wrongly default to MODRDN if DNs are in different formats Status changed from Assigned to Feedback Target version changed from 1.3.x branch to 1.2.2 % Done changed from 0 to 100
I have fixed the BeanComparator's method to determine which operation to apply by making sure the DN comparaison is done after removing the destination's context DN, if present. This should fix the bug described while remaining backwards compatible. The fix has been committed, and will be in tomorrow's nightly 1.2-SNAPSHOT and 1.3-SNAPSHOT, and available in a few minutes on http://build.lsc-project.org/. Ronald, would you test please? Thanks! ---------------------------------------- Bug #264: Operation choice may wrongly default to MODRDN if DNs are in different formats http://tools.lsc-project.org/issues/264 Author: Ronald Rudimor Status: Feedback Priority: High Assigned to: Jonathan Clarke Category: Core Target version: 1.2.2 Problem in version: 1.2.0 When a synchronization with no DN rewrite takes place, lsc is not able to find and match entries in both src and dst. As a result, an attempt to add the entries again is performed. The same bug, probably causes the entries to be deleted (if you don't have .condition.delete = false). -- 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
