Many thanks David, your response correspond to what i understand of LSC behavior.
For the comma character my phpLdapAdmin permit to set it, so i will have to refuse that character. Regards, Le 16/07/13, David Coutadeur <[email protected]> a écrit : > > It seems that DN is case insensitive, but CN is not... > I am not sure how matching rules are set and retrieved on AD. > Issue 342 is still open and correspond quite well to your problem. > > As far as I know, it is highly discouraged to use comma characters in DN > components, in any directory... > Considering this, LSC should manage the comma character. > > Le 16/07/2013 15:01, "POISSON Frédéric" a écrit : > > Hello David, > > > > Yes conditions correspond : > > ... > > <conditions> > > <create>true</create> > > <update>true</update> > > <delete>true</delete> > > <changeId>true</changeId> > > </conditions> > > > > My pivot as source LDAP is Sun DS is nsUniqueID, i map this attribute to > > serialNumber on Active Directory. I see that modrn works when i change CN > > by adding letters, but don't work when changing from/to upper or lower case > > letter. > > > > DN component on destination is "CN={cn},<base Active Directory>". > > > > Notice that i see after sending my email this bug id > > http://tools.lsc-project.org/issues/342 , it seems to be quite similar ? > > > > I have also another question about modrdn, does LSC manage the comma > > character ? > > > > Regards, > > Le 16/07/13, David Coutadeur <[email protected]> a écrit : > >> > >> Hi Frederic, > >> > >> Did you set your changeId condition accordingly ? > >> What is your DN component and your pivot attribute ? > >> > >> > >> <conditions> > >> <create>true</create> > >> <update>true</update> > >> <delete>true</delete> > >> <changeId>true</changeId> > >> </conditions> > >> > >> Regards, > >> David > >> > >> > >> Le 16/07/2013 14:26, "POISSON Frédéric" a écrit : > >>> Hello, > >>> > >>> I'm running some test of synchronization between from a Sun DS to an AD. > >>> I have defined a pivot attribute which permit normally to identify each > >>> entries inside my source. > >>> > >>> When i update an Sun DS entry on attribute cn which is a part of the DN > >>> of the AD entry synced, LSC do a replace ldap operation instead of modrdn > >>> ? The modification done on the source is just replacing lower characters > >>> to upper characters on cn attribute. > >>> > >>> Have you ever encounter this problem ? > >>> > >>> With DEBUG inside logback.xml i see this line : > >>> ... Replacing attribute "cn": source values are [Stephane TEST], old > >>> values were [Stephane test], new values are [Stephane TEST] > >>> > >>> Regards, > >>> PS: I use LSC 2.0.2. > >>> -- > >>> > >>> Frederic Poisson > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________________________ > >>> Ldap Synchronization Connector (LSC) - http://lsc-project.org > >>> > >>> lsc-users mailing list > >>> [email protected] > >>> http://lists.lsc-project.org/listinfo/lsc-users > >> > >> > >> > > -- > > > > Frederic Poisson > > > > > > > -- > David Coutadeur - intégrateur LinID > Groupe LINAGORA - BU LGS > +33 1 46 96 63 63 / poste 601 > +33 6 42 00 63 19 > 80 rue Roque de Fillol > 92800 PUTEAUX > > "/La présente transmission contient des informations confidentielles > appartenant à Linagora, exclusivement destinées au(x) destinataire(s) > identifié(s) ci-dessus. Si vous n'en faites pas partie, toute > reproduction, distribution ou divulgation de tout ou partie des > informations de cette transmission, ou toute action effectuée sur la > base de celles-ci vous sont formellement interdites. > Si vous avez reçu cette transmission par erreur, nous vous remercions de > nous en avertir et de la détruire de votre système d'information. > > The present transmission contains privileged and confidential > information belonging to Linagora, exclusively intended for the > recipient(s) thereabove identified. If you are not one of these > aforementioned recipients, any reproduction, distribution, disclosure of > said information in whole or in part, as well as any action undertaken > on the basis of said information are strictly prohibited. If you > received the present transmission by mistake, please inform us and > destroy it from your messenging and information systems./" > > -- Frederic Poisson
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
