Yes we do use clean filter, which is
<cleanFilter>: (sAMAccountName={sAMAccountName}).
We have also the following filters to sync users
<getAllFilter> - (&(objectCategory=Person))
<getOneFilter> - (&(objectCategory=Person))
<cleanFilter> (sAMAccountName={sAMAccountName})
We have the following filters to sync groups
<getAllFilter> - (&(objectCategory=Group))
<getOneFilter> - (&(objectCategory=Person))
<cleanFilter> (sAMAccountName={sAMAccountName})
All filters are set programmatically and not through the lsc.xml
Is LSC designed in such a way that clean task will honour the filter and won't
clean anything which does not honour nothing outside it? If I want to delete
everything from the destination , even outside the filter, will it be possible?
Regards,
Dinesh Babu.
Pitney Bowes Software
6 Hercules Way, Leavesden Park, Watford, Herts WD25 7GS
Ph: +441923 279123 www.pb.com/software<http://www.pb.com/software>
[email protected]
Every connection is a new opportunity™
[cid:[email protected]]
Please consider the environment before printing or forwarding this email. If
you do print this email, please recycle the paper.
This email message may contain confidential, proprietary and/or privileged
information. It is intended only for the use of the intended recipient(s). If
you have received it in error, please immediately advise the sender by reply
email and then delete this email message. Any disclosure, copying, distribution
or use of the information contained in this email message to or by anyone other
than the intended recipient is strictly prohibited.
From: Clément OUDOT [mailto:[email protected]]
Sent: 23 October 2014 22:12
To: Dinesh Babu
Cc: [email protected]; [email protected]; Steven
Runyeard
Subject: Re: [lsc-users] LSC doesn’t delete records, which does not match the
filter, from the destination repository when the filter is changed
2014-10-23 16:01 GMT+02:00 Dinesh Babu
<[email protected]<mailto:[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
