HI Juan, You are completely right ! I'll fixed it this afterrnoon.
1. No because it is used before the destination bean has been populated 2. The Modify RDN operation is tried because the destinatio entry is found through the filterId criteria but the mainIdentifier does not compute the same value that is found inside the destination entry DN. Regards, 2012/8/14, Juan Carlos Camargo <[email protected]>: > Hi there, > > > I'm new to the product, I got notice of it a few days ago. I've been reading > the documentation for the 2.0 release and I think there's a mistake in this > tutorial: > http://lsc-project.org/wiki/documentation/2.0/tutorials/openldaptoactivedirectory > . It demonstrates the use of connectors to populate AD from OpenLDAP. But in > the config example I've noticed that AD was set as source (source is used to > read) whereas OpenLDAP as destination (destination is used to check and > update), is that correct? > > > Even if it wasn't, I must admit I'm having a bad time trying to clarify > concepts :) Can you please help me? > > > 1.- Can mainIdentifier access the destination bean? > 2.- Why the sync process always try to modify the rdn? In my scenario I dont > need to do that. Let's suppose I have two ldap directories. I link them > together by the user's email address and if they match I simply update an > attribute in destination with data from the source. What is the sense of > modifying the rdn then? > > Thanks a lot :) > > -- > > > > > > > > J u an Carlos Camargo Carrillo > 957-211157 , 650932877 > -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
