Le 18/02/2016 23:26, Jonathon A Anderson a écrit :
I’m using lsc to synchronize ldap trees between two 389-DS servers:
src: 389-ds-base-1.2.11.15-22.el6_4.x86_64
dest: 389-ds-base-1.3.4.0-26.el7_2.x86_64
If I configure these as ldaps://, everything works as expected; but if I configure these as
ldap:// and <tlsActivated>true</tlsActivated>, synchronization happens, but the
process hangs at the end during tlsResponse.close(). (org.lsc.jndi.JndiServices.java:1211)
I’m on lsc-core-2.1.3 (lsc-2.1.3-0.el5.noarch)
I’m willing and able to run further tests to debug this, as I’d prefer it to
work using starttls.
Hi,
seems there is a bug here, could you open an issue on
http://tools.lsc-project.org/projects/show/lsc ?
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
