Le 17 avril 2012 22:15, Sébastien Bahloul <[email protected]> a écrit : > HI guys, > > You are probably both right because you are both power users (and even > more!) and you should be able to use it without any trouble. > > But in fact LSC is covering the specs precised at the following location at > the bottom of the page > : http://lsc-project.org/wiki/documentation/2.0/configuration/syncoptions > > If your source has values and you don't enforce through forceValues > explicitely, the source values are simply reproduced. > If your source does not provide any value then : > - if the entry is created, the createValues will be used if they are > specified > - otherwise the defaultValues will be used > > So : > - Clement: you are look to enforce values without any respect to the source > values, so use a FORCE policy with forceValues.
Are you sur this sill not erase values in destination if they changed? The goal is to create the objectClass attribute with some values, and then never modify it (it can be modified in the destination). The other problem for me, is that my configuration works perfectly with a ldapSourceService but not with asynLdapSourceService. Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
