Issue #201 has been updated by Lanore Ronan.
I think this is a bug beacause , in documentation page: http://lsc-project.org/wiki/documentation/1.2/configuration/task Note: To never change the DN, set this property to ”” (the empty string). In this case, LSC will ignore MODRDN operations. This will also stop LSC from creating objects, since they have no DN. so i don't think that produce an ADD operation?? however i don't remember the "custom condition to create and delete" ---------------------------------------- Bug #201: LSC try to add entries when he has no dn for them http://tools.lsc-project.org/issues/201 Author: Lanore Ronan Status: Rejected Priority: Normal Assigned to: Jonathan Clarke Category: Target version: Problem in version: When i use this configuration line: lsc.tasks.CMUser.dn = "" the directive lsc.tasks.CMUser.condition.modrdn and lsc.tasks.CMUser.condition.update are in default value I have a custom condition to create and delete launch lsc with : lsc -f ../etc -s taskName LSC try to add entries in ldap destination LSC LOG is : _Apr 16 06:58:33 - DEBUG - Synchronizing CMUser for {uid=100037} Apr 16 06:58:33 - DEBUG - In entry "": List of attributes considered for writing in destination: [employeeType, uid, sn, title, ou, cn, shadowExpire, seeAlso, objectClass, givenName, employeeNumber] Apr 16 06:58:33 - DEBUG - In entry "": Attribute "employeeType" is in FORCE status ... ... Apr 16 06:58:33 - DEBUG - In entry "": Attribute "employeeNumber" is in FORCE status Apr 16 06:58:33 - DEBUG - In entry "": Adding attribute "employeeNumber" with values [100037] Apr 16 06:58:33 - ERROR - Error while synchronizing ID : java.lang.IndexOutOfBoundsException: Posn: -1, Size: 0 Apr 16 06:58:33 - DEBUG - java.lang.IndexOutOfBoundsException: Posn: -1, Size: 0 java.lang.IndexOutOfBoundsException: Posn: -1, Size: 0 at javax.naming.ldap.LdapName.getPrefix(LdapName.java:240) [na:1.6.0_12] at com.sun.jndi.toolkit.ctx.Continuation.fillInException(Continuation.java:133) [na:1.6.0_12] at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:812) [na:1.6.0_12] at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319) [na:1.6.0_12] at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248) [na:1.6.0_12] at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:183) [na:1.6.0_12] at org.lsc.jndi.JndiServices.apply(JndiServices.java:521) [lsc-core-1.2-SNAPSHOT.jar:na] at org.lsc.AbstractSynchronize.synchronize2Ldap(AbstractSynchronize.java:390) [lsc-core-1.2-SNAPSHOT.jar:na] at org.lsc.SimpleSynchronize.launchTask(SimpleSynchronize.java:273) [lsc-core-1.2-SNAPSHOT.jar:na] at org.lsc.SimpleSynchronize.launch(SimpleSynchronize.java:156) [lsc-core-1.2-SNAPSHOT.jar:na] at org.lsc.Launcher.run(Launcher.java:147) [lsc-core-1.2-SNAPSHOT.jar:na] at org.lsc.Launcher.main(Launcher.java:123) [lsc-core-1.2-SNAPSHOT.jar:na] dn: dc=domain,dc=fr changetype: add ... ..._ LDAP log: _Apr 16 06:58:33 ref slapd[19972]: conn=219 op=65 ADD dn="dc=domain,dc=fr" Apr 16 06:58:33 ref slapd[19972]: Entry (dc=domain,dc=fr), attribute 'dc' not allowed Apr 16 06:58:33 ref slapd[19972]: conn=219 op=65 RESULT tag=105 err=65 text=attribute 'dc' not allowed Apr 16 06:58:33 ref slapd[19972]: conn=219 fd=18 closed (connection lost)_ -- 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
