Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Connecting from Config Client to Config Server using self-signed certificates

See original GitHub issue

Is there a way for a config client to connect to a config server if the config server is using self-signed certificates? The idea here is to use self-signed for local testing, then use real certificates in production. Is there a property on the client side that can be used to have it relax?

Client’s exception, when attempting to connect to the config server, is:

2015-05-11 11:47:47.948 ERROR 41554 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for "https://localhost:8443/subject/subject/master":java.security.cert.CertificateException: No name matching localhost found; nested exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching localhost found

Issue Analytics

State:
Created 8 years ago
Comments:19 (10 by maintainers)

Top GitHub Comments

1reaction

eugenebellcommented, May 12, 2015

Have you tried to run a command like the following? git config http.sslVerify false This will set the sslverify to false in the .git/config file [http] sslVerify = false

0reactions

dsyercommented, May 5, 2016

Git and SSH configuration is already mentioned in the user guide. Connecting to the config server over HTTPS is really out of the scope of Spring Cloud Config.