-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
-
generic
-
generic
ADDITIONAL SYSTEM INFORMATION :
JDK17/JDK21
A DESCRIPTION OF THE PROBLEM :
When overriding the default truststore using Djavax.net.ssl.trustStore, if an invalid path is provided no error is thrown up to the running application to indicate this. Instead it looks like the Certificate libraries will silently fail and load the DummyX509TrustManager.
The client should be aware that the truststore provided could not be found, with a fileNotFound or key/truststore error.
Could this be looked into and verified/raised? It feels like this would be relevant to a number of issues and posts raised on the web relating to misconfigured paths.
JDK17/JDK21
A DESCRIPTION OF THE PROBLEM :
When overriding the default truststore using Djavax.net.ssl.trustStore, if an invalid path is provided no error is thrown up to the running application to indicate this. Instead it looks like the Certificate libraries will silently fail and load the DummyX509TrustManager.
The client should be aware that the truststore provided could not be found, with a fileNotFound or key/truststore error.
Could this be looked into and verified/raised? It feels like this would be relevant to a number of issues and posts raised on the web relating to misconfigured paths.