2014-11-25 10:19 GMT+01:00 FOUCHET, Alexandre < [email protected]>:
> No, I am not using asyncLdapSourceService(and by extension, I don’t use > Syncrepl), I use ldapSourceService and ldapDestinationService. > > I have installed LSC with RPM, configuration seems to be OK by default. > Only weird I wonder about, is that the RPM has created a “lsc” user and > group, but they are never used anywhere (all filles in /usr/bin/lsc & > /etc/lsc/* are all belonging to root:root with 755). > They are used to launch lsc service. If you don't use asyncLdapSourceService, you can't get changes on the fly. In this case, use /etc/cron.d/lsc to parameter the frequency of LSC run. > > > Lsc.log contains nothing special : > > “Nov 25 10:06:17 - INFO - Logging configuration successfully loaded from > /etc/lsc/logback.xml > > Nov 25 10:06:17 - INFO - LSC configuration successfully loaded from > /etc/lsc/ > > Nov 25 10:06:17 - INFO - Configuration and environment successfully > checked ! > > 2014/11/25 10:06:17 [lsc] Starting LSC > > 2014/11/25 10:06:17 [lsc] Using JMX port 1099 > > Nov 25 10:06:18 - INFO - Logging configuration successfully loaded from > /etc/lsc/logback.xml > > Nov 25 10:06:18 - INFO - LSC configuration successfully loaded from > /etc/lsc/ > > Nov 25 10:06:18 - INFO - Connecting to LDAP server > ldap://10.xxx.xxx.xxx:389/dc=ad,dc=fr as cn=lfradmin,dc=ad,dc=fr > > Nov 25 10:06:18 - INFO - Connecting to LDAP server > ldap://localhost:389/dc=ad,dc=fr as cn=lfradmin,dc=ad,dc=fr” > > > > Lsc.status contains the same. Lsc.ldif contains all the objects that LSC > has synchronized, *changetype is always add.* > > > > Do I need to be using a special version of LDAP for update / delete to > work ? > > > Maybe LSC does not found the corresponding entry in the destination and try to add all entries. Check the getOneFilter of your destination service. > My ldap connections are defined as : > > <referral>IGNORE</referral> > > <derefAliases>NEVER</derefAliases> > > <version>VERSION_3</version> > > <pageSize>-1</pageSize> > > <factory>com.sun.jndi.ldap.LdapCtxFactory</factory> > > <tlsActivated>false</tlsActivated> > > Which I think are default values. > > > > <propertiesBasedSyncOptions> > > <mainIdentifier>"uid=" + srcBean.getDatasetFirstValueById("uid") + > ",dmdName=users,dmdName=community,dmdName=portal,dmdName=applications,dc=cap,dc=ad"</mainIdentifier> > > <defaultDelimiter>;</defaultDelimiter> > > <defaultPolicy>FORCE</defaultPolicy> > > <conditions> > > <create>true</create> > > <update>true</update> > > <delete>true</delete> > > <changeId>false</changeId> > > </conditions> > > [no datasets] > > </propertiesBasedSyncOptions> > > > > Do I absolutely need to define datasets in order to have the value from > the source LDAP to be updated to the dest LDAP ? > No, you can skip dataset if the attribute is defined in fetchedAttribute in source and destination and no adaptation is needed. > > > Once again thanks for your help, I just need a little bit more to fix that > delete / update stuff! > Maybe you should send your whole lsc.xml, without the passwords. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
