Problem
Attempting to configure a Custom Protocol (including http/https)
Connection using HTTPS fails with one of the below stacktraces.
java.lang.RuntimeException: Cannot create connection. Reason is java.security.cert.CertificateException: No name matching hostname.com found, No name matching hostname.com found
at datameer.dap.sdk.datastore.FileDataStoreModel.testConnect(FileDataStoreModel.java:63)
at datameer.dap.sdk.datastore.FileDataStoreModel.testConnect(FileDataStoreModel.java:47)
at datameer.dap.sdk.entity.DataStore.validate(DataStore.java:208)
...
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching hostname.com found
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
...
Caused by: java.security.cert.CertificateException: No name matching hostname.com found
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:231)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
or
java.lang.RuntimeException: Cannot create connection. Reason is java.security.cert.CertificateException: No subject alternative names present, No subject alternative names present
at datameer.dap.sdk.datastore.FileDataStoreModel.testConnect(FileDataStoreModel.java:63)
at datameer.dap.sdk.datastore.FileDataStoreModel.testConnect(FileDataStoreModel.java:47)
at datameer.dap.sdk.entity.DataStore.validate(DataStore.java:208)
...
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names present
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
...
Caused by: java.security.cert.CertificateException: No subject alternative names present
at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:145)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:94)
Cause
Often this behaviour is caused by the fact that the service you are trying to connect to doesn't have a proper SSL certificate or the hostname set within the Base URL property doesn't match with the hostname indicated at the SSL certificate.
Solution
Ensure that the service you are trying to connect to has proper chain of SSL certificates installed and the <hostname>:<port> specified in the Connection settings (Base URL) is correct.
Comments
0 comments
Please sign in to leave a comment.