On 02/04/2016 15:21, Nisreen wrote:
Thanks alot for your reply, would you please elaporate more on the second
point, do you mean i can edit the ldap connid connector in a way that will
support The SYNC operations?
Of course, no :-)
For having a given connector to support SYNC, someone needs to code the
logic that parses and reports about the given technology's changelog: at
the moment the ConnId LDAP connector only supports this for Oracle DSEE
/ RedHat 389 / OpenDJ - and the relevant classes are available at [1].
Should you need proper support for IBM TDS, you'll have to fork the
ConnId LDAP connector [2], add your code there and maybe eventually
request to have it merged back.
What I was referring to in my previous reply is the possibility - having
clear your own specific requirements - to adjust the overall
synchronization process by providing your own SyncActions classes [3].
Clearly, which logic is to code into such classes cannot be stated in
general here, but heavily depends on your organization's internal processes.
HTH
Regards.
[1]
https://github.com/Tirasa/ConnIdLDAPBundle/tree/master/src/main/java/net/tirasa/connid/bundles/ldap/sync/sunds
[2] https://github.com/Tirasa/ConnIdLDAPBundle
[3] https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer
http://home.apache.org/~ilgrosso/
