Hi Sébastien, i am sorry but i don't really understand how to do that. Have you got an example about that because i don't know what other configuration in the destination i could use.
Regards Le Mercredi 15 Août 2012 23:13 CEST, Sébastien Bahloul <[email protected]> a écrit: > Hi Guys, > > I don't think that switching to a async task type would solve your issue. > The way you need to configure LSC is to give a base and a filter in the > destination directory that enables LSC to find the entry and to write a > mainIdentifier that will match your obso OU. LSC will "rename" the entry to > move it to the correct location. > > Regards, > -- > Sebastien BAHLOUL > IAM / Security specialist > Ldap Synchronization Connector : http://lsc-project.org > Blog : http://sbahloul.wordpress.com/ > > > > 2012/8/15 dunkan <[email protected]> > > > Run your job as -a instead of -s. For example bin/lsc -f etc -a all > > > > -Joel > > > > > > On Wed, Aug 15, 2012 at 9:13 AM, Yahiaoui Hakim < > > [email protected]> wrote: > > > >> Thanks, it is my problem. > >> I know the entry already exists in another organisational unit but i just > >> want it updates moving the entry in the new organisational unit. > >> How do you do for running it as an async job? > >> > >> Regards > >> > >> > >> > >> Le Mercredi 15 Août 2012 05:13 CEST, dunkan <[email protected]> a écrit: > >> > >> > Hello, > >> > > >> > I believe there is a bug with sync jobs, try running it as an async job > >> to > >> > see if it updates. I believe that is the problem you are having right? > >> It > >> > says the entry already exists rather then just updating the values? > >> > > >> > -Joel > >> > > >> > On Tue, Aug 14, 2012 at 5:35 AM, Yahiaoui Hakim < > >> > [email protected]> wrote: > >> > > >> > > Hi, > >> > > > >> > > I have entries in a people OU . > >> > > I have an "obso" OU where people entries go when the account is > >> finished. > >> > > > >> > > When i synchronise obso OU of my OpenLdap whith obso OU of my AD, it > >> tell > >> > > me that entry already exist! > >> > > > >> > > Is it possible not have this error and lsc just move the > >> > > entry in the other ou? > >> > > > >> > > My configuration : > >> > > > >> > > <task> > >> > > <name>people</name> > >> > > <bean>org.lsc.beans.SimpleBean</bean> > >> > > <ldapSourceService> > >> > > <name>opends-source-service</name> > >> > > <connection reference="ldap-src-conn" /> > >> > > <baseDn>ou=people,dc=myOpenLdap,dc=fr</baseDn> > >> > > <pivotAttributes> > >> > > <string>uid</string> > >> > > </pivotAttributes> > >> > > <fetchedAttributes> > >> > > <string>objectClass</string> > >> > > <string>cn</string> > >> > > <string>sn</string> > >> > > <string>displayName</string> > >> > > <string>uid</string> > >> > > <string>mail</string>> > >> > > </fetchedAttributes> > >> > > <getAllFilter>(objectClass=inetOrgPerson)</getAllFilter> > >> > > <getOneFilter>(uid={uid})</getOneFilter> > >> > > </ldapSourceService> > >> > > <ldapDestinationService> > >> > > <name>openldap-dst-service</name> > >> > > <connection reference="ldap-dst-conn" /> > >> > > <baseDn>ou=People,dc=myAD,dc=local</baseDn> > >> > > <pivotAttributes> > >> > > <string>sAMAccountName</string> > >> > > </pivotAttributes> > >> > > <fetchedAttributes> > >> > > <string>objectClass</string> > >> > > <string>cn</string> > >> > > <string>sn</string> > >> > > <string>displayName</string> > >> > > <string>sAMAccountName</string> > >> > > <string>mail</string> > >> > > </fetchedAttributes> > >> > > <getAllFilter></getAllFilter> > >> > > <getOneFilter>(sAMAccountName={uid})</getOneFilter> > >> > > </ldapDestinationService> > >> > > <propertiesBasedSyncOptions> > >> > > <mainIdentifier>"cn=" + > >> srcBean.getDatasetFirstValueById("uid") + > >> > > ",ou=People,dc=myAD,dc=local"</mainIdentifier> > >> > > <defaultDelimiter>;</defaultDelimiter> > >> > > <defaultPolicy>FORCE</defaultPolicy> > >> > > <conditions> > >> > > <create>true</create> > >> > > <update>true</update> > >> > > <delete>true</delete> > >> > > <changeId>false</changeId> > >> > > </conditions> > >> > > <dataset> > >> > > <name>objectClass</name> > >> > > <policy>FORCE</policy> > >> > > <forceValues> > >> > > <string>"top"</string> > >> > > <string>"person"</string> > >> > > <string>"organizationalPerson"</string> > >> > > <string>"user"</string> > >> > > </forceValues> > >> > > <delimiter>;</delimiter> > >> > > </dataset> > >> > > <dataset> > >> > > <name>sAMAccountName</name> > >> > > <policy>FORCE</policy> > >> > > <forceValues> > >> > > <string>srcBean.getDatasetFirstValueById("uid")</string> > >> > > </forceValues> > >> > > </dataset> > >> > > <dataset> > >> > > <name>cn</name> > >> > > <policy>FORCE</policy> > >> > > <forceValues> > >> > > <string>srcBean.getDatasetFirstValueById("uid")</string> > >> > > </forceValues> > >> > > </dataset> > >> > > <dataset> > >> > > <name>default</name> > >> > > <policy>FORCE</policy> > >> > > </dataset> > >> > > </propertiesBasedSyncOptions> > >> > > </task> > >> > > > >> > > > >> > > Regards > >> > > > >> > > > >> > > _______________________________________________________________ > >> > > Ldap Synchronization Connector (LSC) - http://lsc-project.org > >> > > > >> > > lsc-users mailing list > >> > > [email protected] > >> > > http://lists.lsc-project.org/listinfo/lsc-users > >> > > > >> > >> > >> > >> > >> > >> > > > > _______________________________________________________________ > > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > > > lsc-users mailing list > > [email protected] > > http://lists.lsc-project.org/listinfo/lsc-users > > > > _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
