Issue #124 has been updated by J?r?me Schell.
I resolved my problem for now by renaming the key attribute in the database table to "uid" instead of "logname". This way it all seems to work ok. My primary interrogation is still valid. What is the good configuration to have the clean and sync phase working when the keys have different name in database and LDAP? ---------------------------------------- Bug #124: Clean phase of db2ldap deletes all entities http://tools.lsc-project.org/issues/show/124 Author: J?r?me Schell Status: New Priority: High Assigned to: Category: Core Target version: During the clean phase of a db2ldap job, all entities in the destination are deleted. After tracking the problem a bit, it seems that the method clean2Ldap of org.lsc.AbstractSynchronize loops on all destination entries and calls the getObject method of org.lsc.service.AbstractJdbcService passing it the id of the entry (to look for it in the source). The problem is that the format of the id is the DN of the LDAP entry (uid=john.do,dc=mydomain,dc=com) and in the case of a JDBC source, that value is irrelevant. -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20091014/ddbff417/attachment-0001.htm>
