Hi Hakim, Consider moving to ldapSourceService instead of asyncLdapSourceService which will not be fully stable on this 2.0rc2 version.
Regards -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ 2012/6/18 yahiaoui hakim <[email protected]> > ** > Hi Sebastien, > > thanks for answer so quickly! > > there is my task : > > <task> > <name>people</name> > <bean>org.lsc.beans.SimpleBean</bean> > <asyncLdapSourceService> > <name>opends-source-service</name> > <connection reference="ldap-src-conn" /> > <baseDn>ou=people,dc=mydomain,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> > <serverType>OpenDS</serverType> > </asyncLdapSourceService> > <ldapDestinationService> > <name>openldap-dst-service</name> > <connection reference="ldap-dst-conn" /> > <baseDn>ou=People,dc=mydomain,dc=local</baseDn> > <pivotAttributes> > <string>sAMAccountName</string> > </pivotAttributes> > <fetchedAttributes> > <string>objectClass</string> > <string>cn</string> > <string>sn</string> > <string>displayName</string> > <string>uid</string> > <string>sAMAccountName</string> > <string>mail</string> > </fetchedAttributes> > <getAllFilter>(objectClass=inetorgperson)</getAllFilter> > <getOneFilter>(sAMAccountName={uid})</getOneFilter> > </ldapDestinationService> > <propertiesBasedSyncOptions> > <mainIdentifier>"cn=" + srcBean.getDatasetFirstValueById("uid") + > ",ou=People,dc=mydomain,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>"inetOrgPerson"</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 > > Le 15/06/2012 17:22, Sébastien Bahloul a écrit : > > Hi Hakim, > > Can you pastebin the corresponding task of your configuration file ? > > Regards, > -- > Sebastien BAHLOUL > IAM / Security specialist > Ldap Synchronization Connector : http://lsc-project.org > Blog : http://sbahloul.wordpress.com/ > > > From: yahiaoui hakim <[email protected]> >> To: [email protected] >> Cc: >> Date: Fri, 15 Jun 2012 16:03:15 +0200 >> Subject: Problem with lsc 2.0rc2 >> Hi, >> >> I use lsc 2.0rc1 without problems. >> I want now use lsc 2.0rc2 but there are errors. >> >> I use the same lsc.xml file but when i run, i have following errors: >> >> juin 15 15:58:28 - WARN - No clean filter has been specified for >> task=people. During the clean phase, LSC wouldn't be able to get the right >> entries and may delete all destination entries ! >> juin 15 15:58:29 - INFO - Starting sync for people >> juin 15 15:58:29 - ERROR - Empty or non existant source (no IDs found) >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> juin 15 15:58:30 - WARN - The PDU has been fully decoded but there are >> still bytes in the buffer. >> .................................... >> .................................... >> .................................... >> >> >> As many errors as entries! >> Could you please help me? >> >> Thanks >> >> > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing > [email protected]http://lists.lsc-project.org/listinfo/lsc-users > > > > -- > Hakim YAHIAOUI > > Université Jean Monnet Saint-Etienne > Direction du Système d'Information - DSI > Ingénieur d'étude du Pôle Système, Réseau et Sécurité - SRS > > 21, rue du Docteur Paul Michelon > 42023 Saint ETIENNE > > Tél : 04 69 66 31 24 > >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
