2014-10-23 16:01 GMT+02:00 Dinesh Babu <[email protected]>: > > > Hi, > > > > We current have a problem where our sync process doesn’t delete > appropriate records from the destination repository when the filter is > changed. > > > > If we initially configure our filter to sync all entries within LDAP with > our repository and then for subsequent syncs modify the filter so that only > a subset of the LDAP content is synced with the destination repository, the > entries within the repository which do not conform to the new filter are > still left behind. I presume this occurs because the filter effectively > hides the entries that do not conform to the filter as far as LSC is > concerned so it’s effectively unaware of their existence. > > > > My intended fix is to store the filter that was used for the sync and then > subsequent syncs then first check to see if the filter has changed. If it > has changed then the destination repository is completely wiped before the > sync is performed. This does sound like a heavy-handed way of dealing with > the problem. Is there a simpler way to achieve the result of removing > entries from the destination that do not match the filter? >
Hi, did you use the "cleanFilter" configuration parameter? Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
