[lsc-users] Synchronization of a single attribute
sebastien.bahloul at gmail.com
Thu Sep 29 21:32:29 CEST 2011
This is a quite interesting feature, that does not exist at this time: the
only way to handle a non existing entry in the source for LSC is to delete
it in the destination.
You may write your own Jndi destination service that will handle a delete
event in a way that fits your requirements (deleting an attribute instead of
deleting an entry). Please feel free to fill a feature request
IAM / Security specialist
Ldap Synchronization Connector : http://lsc-project.org
Blog : http://sbahloul.wordpress.com/
2011/9/29 Maxime Pelletier <maxime.pelletier at educsa.org>
> Hi all,
> I'm currently facing a problem for which I can't find a clean solution so
> I'd like to know if any of you could help us.
> I have a source DB in which is stored data about employee to class number
> relationship. With this DB, I populate the attribute "classNumber" in LDAP.
> However, not all employee have class number, and when they don't, they are
> not in my source DB.
> What is causing problem is that when a user is not associated with a class
> number anymore, this user is not in the source DB anymore and then won't be
> updated at all by the task. As a result, this user will still be associated
> with the last class number he was associated to.
> I want to delete the attribute only, not the whole entry so including all
> entries in the "filterAll" and adding "-c all" won't really help me as this
> would delete the entry.
> The only solution I found would be to use a "flag" attribute telling me
> that an entry was found in the source DB. I could then delete the attribute
> for all entries where there is a value but without the flag.
> Well, I hope that you understand my problem:) Let me know if you have any
> idea for me!
> Ldap Synchronization Connector (LSC) - http://lsc-project.org
> lsc-users mailing list
> lsc-users at lists.lsc-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lsc-users