Clément,
Thank you so much for the reply. This helps me a lot.
Please forgive me for my next question, because I do not have a lot of
experience with AD and LDAP.
The RFC-4530 <https://tools.ietf.org/html/rfc4530> specification
indicates the entryUUID attribute is optional. Is this generally
implemented in most systems? The tool we're working on we are hoping to
deploy in many different environments in order to give them a way to
synchronize their servers to our proprietary API.
If entryUUID isn't used, is there another commonly used unique identifier?
It would appear for AD I should be able to use the objectGUID (or would
objectSID be better)?
Thanks!
-Dan
On 10/7/2015 3:37 AM, Clément OUDOT wrote:
Hi Dan,
You can trim the dataset but pivotValues are not modified. We added
such feature for the next release (2.2, see
http://tools.lsc-project.org/issues/756) but we can't say when it will
be ready.
Maybe the solution is to have a first connector that wil trim the
values in your source, using a different pivot (if the source is LDAP,
you can use entryUUID), and then use the second connector to
synchronize to HSQLDB.
--
Dan G. Switzer, II
Giva, Inc.
Email: [email protected]
Web Site: http://www.givainc.com
See Our Customer Successes
http://www.givainc.com/customers-casestudies.htm
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
