Closed douglas-andrew-harley closed 6 years ago
OK, I got this certificates issue resolved (still cannot commit files to SolrCloud yet, because of auth issues)...our IT person had given me incorrect certs, for a different tier. In the end I ahd to download the cert myself, and import it into the trustore using keytool. Adding this info here in case others get stuck also (replace HOSTNAME, TRUSTSTORENAME, and ALIASNAME for your values):
1) get server cert: openssl x509 -in <(openssl s_client -connect HOSTNAME:443 -prexit 2>/dev/null) -out HOSTNAME.crt
2) import the certificate: keytool -importcert -file HOSTNAME.crt -alias ALIASNAME-keystore TRUSTSTORENAME
Cheers, Doug
Glad you found a way and thanks for sharing. Have you tried this setting as well?
<httpClientFactory>
<trustAllSSLCertificates>true</trustAllSSLCertificates>
</httpClientFactory>
Your way of doing it is best, but that option is there if you need it.
Would you say this issue can be closed?
No, I didn't try that setting...thanks though. Yes, please feel free to close.
Cheers, Doug
Hello, Upon attempting to commit documents to a SolrCloud cluster running behind an NGINX reverse-proxy setup to use HTTPS, I get the exceptions below. I have added the server's wildcard cert to the cacerts trustore, and specified the require JVM args:
-Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/usr/lib/jvm/java-8-oracle/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit
I can list with keytool and see my cert, and when i move the cacerts file the HTTP crawler immediately fails similary, because the site I am crawling also runs HTTPS.
Any ideas what might be going on here? Anyone had any luck pushing to SolrCloud behind HTTPS?
Thanks, Doug