Le 24/08/2018 à 16:30, ERIC BRYS a écrit : > > Hello, > > >
Hello Eric, > We installed the last version LSC core 2.1.4 for a POC to replace our > old Maxware DSE solution for LDAP synchronization. > > We are testing different scenarios. > > One of them must be able to keep current objectClass attribute’s > values for an existing destination entry, and not take in account the > source objectClass’s values, > > while if the entry doesn’t exist on the destination and must be > created, the objectClass attribute should be created with the > <createValues/>. > > For this we configured the dataset as follow: > > > > <dataset> > > <name>objectClass</name> > > <policy>KEEP</policy> > > <defaultValues> > > </defaultValues> > > <forceValues> > > </forceValues> > > <createValues> > > <string>"top"</string> > > <string>"person"</string> > > <string>"organizationalperson"</string> > > <string>"inetorgperson"</string> > > <string>"picpersonclass"</string> > > </createValues> > > </dataset> > > > > When running the task, if LSC must create a new entry in the > destination, it does this with the source objectclass’s values and not > the listed <createValue/> ?! > > Keeping the current destination values for an existing entry is > working correctly. > > Any advise to help us to correctly configure this will be appreciate. > > > > You need to remove objectClass from fetchedAttributes in source service, and have it only in fetchedAttributes in destination service. -- Clément Oudot | Identity Solutions Manager [email protected] Worteks | https://www.worteks.com
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
