Issue #85 has been updated by Clément OUDOT.

It seems the problem is still here:

<pre>
avr. 20 09:54:10 - WARN  - WARNING: updating the RDN of the entry will cancel 
other modifications! Relaunch synchronization to complete update.
avr. 20 09:54:10 - INFO  - # Renaming object uid=charles.patr,ou=people,ou=XXX 
for agent
dn: uid=charles.patr,ou=people,ou=XXX
changetype: modrdn
newrdn: initials=charles.patr
deleteoldrdn: 1
newsuperior: ou=people,ou=XXX
</pre>

We have a deleteoldrdn set to 1, is this configurable somewhere? Or maybe 
should we force this option to 0?

Other question: the above operation was done with an asyncLdapSourceService. As 
this is a "daemon mode", the warning "WARNING: updating the RDN of the entry 
will cancel other modifications! Relaunch synchronization to complete update." 
is confusing: we are not supposed to restart a daemon just to apply updates... 
Does this mean the the modrdn is not fully compatible with 
asynLdapSourceService?


----------------------------------------
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

Reply via email to