Issue #85 has been updated by Clément OUDOT.
> We have a deleteoldrdn set to 1, is this configurable somewhere? Or maybe > should we force this option to 0? See http://docs.oracle.com/javase/jndi/tutorial/ldap/misc/rename.html JNDI provide a property called @java.naming.ldap.deleteRDN@, we should add this to the connection or service configuration. ---------------------------------------- Bug #85: MODRDN operation deletes previous RDN http://tools.lsc-project.org/issues/85 Author: Jonathan Clarke Status: Assigned Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 2.0 Problem in version: With the following entry: <pre> dn: cn=CN0001,ou=Test Data,dc=lsc-project,dc=org objectClass: person objectClass: top cn: CN0001 sn: SN0001 </pre> And lsc.properties like this: <pre> lsc.tasks.mytask.dn = "sn=" + srcBean.getAttributeValueById("sn") + ",ou=ldap2ldap2TestTaskDst,ou=Test Data,dc=lsc-project,dc=org" </pre> MODRDN operation should be performed but fails with: <pre> [LDAP: error code 65 - The modify DN operation for entry cn=CN0001,ou=ldap2ldap2TestTaskDst,ou=Test Data,dc=lsc-project,dc=org cannot be performed because the change would have violated the server schema: Entry sn=SN0001,ou=ldap2ldap2TestTaskDst,ou=Test Data,dc=lsc-project,dc=org violates the Directory Server schema configuration because it is missing attribute cn which is required by objectclass person]; remaining name 'cn=CN0001,ou=ldap2ldap2TestTaskDst,ou=Test Data' </pre> It is therefore impossible to do some MODRDN operations. -- 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
