Le 13/09/2016 à 16:32, Bruno MORAZZONI a écrit :
Hi All!
Hello Bruno,
I am trying to implement LSC in order to synchronize two different
LDAP servers, but I have some troubles!
The idea behind it is to populate one "master" LDAP server with all
entries from a "slave" server and maintain them up to date.
Names of the attributes are different, so I need to "translate" them.
To explain a bit more, here are the two tables:
SLAVE MASTER
cn <-> cn
e164 <-> telephonenumber
loc <-> node
Since I am a newbie in both LDAP and LSC, I am trying to go step by step.
From what I understand reading at the doc, my pivot attribute would
either be cn or e164.
Yes, but using cn seems more appropriate.
But this is where I get lost.
Here is the following configuration I am using:
When I launch it using the command:
D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\bin\lsc.bat -f
D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\ip6010to8770 -s all -c all -n
I get the following:
D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\bin>lsc.bat -f
D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\ip6010to8770 -s all -c all -n
sept. 13 15:19:45 - INFO - Logging configuration successfully loaded
from D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\ip6010to8770\logback.xml
sept. 13 15:19:45 - INFO - LSC configuration successfully loaded from
D:\LSC\lsc-core-2.1.3-dist\lsc-2.1.3\ip6010to8770\
sept. 13 15:19:45 - INFO - Connecting to LDAP server
ldap://localhost:389/o=THALES,o=directoryRoot as cn=Directory Manager
sept. 13 15:19:45 - INFO - Connecting to LDAP server
ldap://10.226.90.130:389/ as thales
sept. 13 15:19:48 - ERROR -
org.lsc.exception.LscConfigurationException: Configuration exception: null
Please look up the log file
C:\Users\A0002561\AppData\Local\Temp\2\lsc.log to see the error
But no more logs...
Is there a way to have LSC be more verbose?
Edit the logback.xml file that is in the same directory as lsc.xml and
set all appender to DEBUG.
Do you see something in my config file that could explain the issue?
Not really, but your datasets are wrong. You need to set the correct
objectClass values in objectClass dataset, and add objectClass to
fetchedAttribute of destination service.
Then for e164 attribute, you need to map it to telephoneNumber by
creating a dataset.
--
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
lsc-users@lists.lsc-project.org
http://lists.lsc-project.org/listinfo/lsc-users
