Le 07/06/2016 07:58, Cazanaru, Florin a écrit :
Hi Clement,
Thank you for your answers. What I did till now is:
Sync AD with an openldap – OK with lsc -s all ( I have an working
config and I know how to do it)
But what I do not know/understand is the xml file like:
Here I understand it need to be the connection to AD and LDAP
<connections>
Connection 1 with all requirements
Connection 2 with all requirements
</connections>
Next one is
<audits>
</audits>
At this moment I do not use it.
Last one is tasks and here I have some problems:
<tasks>
<task>
<ldapSourceService>
Preaty clear with name connection, basedn, etc
<pivotAttributes>
Here I understand 75% from what it need but it is ok
</pivotAttributes>
</ldapSourceService>
<ldapDestinationService>
Same like Source
</ldapDestinationService>
<propertiesBasedSyncOptions>
<mainIdentifier>
*I do not know what is doing but I suppose it is for syncronize and
here you have a full path of what you want to syncronize. *
*It is true ?*
</mainIdentifier>
mainIdentifier will allow you to build the destination identifier, which
is a DN for an LDAP destination service
<conditions>
All true to create, update, delete, change
</conditions>
<dataset>
Here you put what you want to sync and
from what and where pretty clear.
</dataset>
</propertiesBasedSyncOptions>
</tasks>
</task>
Ok till now but where I need to put
<asyncLdapSourceService>
</asyncLdapSourceService>
How is the correct combination ? It need to be in <task> after
<ldapSourceService> and <ldapDestiantionService> ?
asyncLdapSourceService is a kind of service, use it to replace
ldapSourceService. But as I said, it will not work for AD.
If I want to sync from AD to ldap is need only <ldapSourceService> and
<ldapDestiantionService> ?, in this case where is the trigger who tell
lsc if the AD make a change on a field ? if I start with service lsc
start, and I want mode then 6 seconds (after I modify a field) lsc did
not do anything to resync that field. If I start with lsc –a all I see
at every 6 seconds LSC wait for something but how it`s works ?
Don't use service lsc start, it is only intersting with a source service
compatible with async. Launch lsc commands in cron.
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
87, rue de Turbigo - 75003 PARIS
Blog: http://sflx.ca/coudot
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
