Issue #248 has been updated by Raphaël Ouazana. Status changed from Assigned to Feedback Assigned to changed from Raphaël Ouazana to Clément OUDOT % Done changed from 0 to 70
I don't think dereferencing aliases in LSC is a good idea, especially in a destination service. Anyway fixed. ---------------------------------------- Bug #248: dn error when using derefAlias = always http://tools.lsc-project.org/issues/248 Author: Lanore Ronan Status: Feedback Priority: Normal Assigned to: Clément OUDOT Category: Core Target version: 2.1 Problem in version: it appears that when we use this config line: <pre> dst.java.naming.ldap.derefAliases = always </pre> in conjunction with an ldap object same as: <pre> # r.lanore, zimbra, applications, dom.fr dn: uid=r.lanore,ou=zimbra,ou=applications,dc=dom,dc=fr objectClass: extensibleObject objectClass: alias objectClass: top uid: r.lanore aliasedObjectName: uid=rlanore,ou=utilisateurs,dc=dom,dc=fr </pre> and this config line: <pre> lsc.tasks.account.dn = "" </pre> produce this log: <pre> Jun 24 18:39:42 - DEBUG - In entry "ldap://localhost:389/uid=rlanore,ou=utilisateurs,dc=cam,dc=fr,ou=zimbra,ou=applications"; </pre> the result should be <pre> Jun 24 18:39:42 - DEBUG - In entry "uid=rlanore,ou=utilisateurs,dc=cam,dc=fr" </pre> no? -- 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
