Le 30/04/2019 à 15:12, Clément OUDOT a écrit :
Le 30/04/2019 à 14:56, Julien TEHERY a écrit :
I imported the certificate exactly as i did in
/etc/ssl/certs/java/cacerts
(it's a self signed certificate with correct CN) matching with the
named uses in LSC's connector
and I still have the same error i don't know why.
Is there a way to bypass the certificate verification ?
You can't. The issue seems linked to "localhost", you can't use this as
valid name for a certificate (as far as I understand in Java SSL check
code:
https://www.mkyong.com/webservices/jax-ws/java-security-cert-certificateexception-no-name-matching-localhost-found/)
You should user a real name (like myserver.example.com) and set this
name in CN field of your self signed certificate.
Ok.
Actually I don't have a problem with the destination certificate (the
servers which runs lsc itself)
Both LSC connectors (remote source and local destination) are well
configured with FQDNs (which matches CNs in SSL certificates)
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
