I have a java server that is trying to connect to an external Ldap server through SSL (as a client in order to perform queries).
I'm having trouble connecting since the certificate they send me upon connecting is trusted only in my local windows Truststore but is not present in java truststore (cacerts).
Is there a way to tell Java to trust any certificate that windows would have trust?
Or, alternatively, is there a way to import all trusted certificates from windows truststore to Java's cacerts?
Any idea would be appreciated.
On Windows, set the following JVM properties:
javax.net.ssl.trustStore=NUL
javax.net.ssl.trustStoreType=Windows-ROOT
I’ve successfully tested this with Java 7, which runs on a 64-bit Windows installation which trusts a self-signed CA.
If the above solution works for you (it should), you may skip this section. Otherwise, check the setup of your Java Cryptography Extension (JCE), which is bundled with modern JDKs. Your JDK installation should have a property file which contains a list of security providers. The location of that file may vary with Java versions; mine is located at "%JAVA_HOME%\jre\lib\security\java.security"
. Inside that file, locate a set of properties whose names begin with security.provider
. One of those entries should be set to sun.security.mscapi.SunMSCAPI
.
To set the properties at runtime, use the following Java code:
System.setProperty("javax.net.ssl.trustStore", "NUL");
System.setProperty("javax.net.ssl.trustStoreType", "Windows-ROOT");
On Windows, Java ships with SunMSCAPI, a security provider which is actually a wrapper around the Windows CAPI.
Setting the javax.net.ssl.trustStoreType
property to Windows-ROOT
instructs Java to refer to the native Windows ROOT keystore for trusted certificates, which includes root CAs. (Similarly, setting javax.net.ssl.keyStoreType
to Windows-MY
tells Java to refer to the native Windows MY keystore for user-specific certificates and their corresponding keys).
If the javax.net.ssl.trustStoreType
property is set to Windows-ROOT
, one would expect that the value of javax.net.ssl.trustStore
is ignored, and that it can be set to e. g. NONE
.
One common workaround for this issue is to set javax.net.ssl.trustStore
to NONE
, and then creating a dummy file whose file name is NONE
. If you find yourself affected by this quirk, try setting javax.net.ssl.trustStore
to NUL
so you won’t have to create any dummy files.