/
Weblogic - failed hostname verification check . Certificate contained ...
Weblogic - failed hostname verification check . Certificate contained ...
Problem
When using the SeaLights test listener as a javaagent in Weblogic, it fails to load with a 'failed hostname verification check' certificate issue.
... <Certificate chain received from hostname - xxx.xxx.xxx.xxx --> app.sealights.co failed hostname verification check. Certificate contained *.sealights.co but check expected app.sealights.co>
Solution
As the SeaLights certificate is a general certificate for *.sealights.co
servers, if Weblogic is set up to perform a hostname verification then this will fail.
Therefore you should turn off this verification in Weblogic
You can turn off the hostname verification by going to:
The Administration Console
Click on Lock & Edit
Expand Environment and select Servers
Select the server
Go to Configuration→SSL→Advanced
Under Hostname Verification select none
Related articles
, multiple selections available,
Related content
WebSphere - Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory
WebSphere - Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory
More like this
Java - Adding Certificate to the Java keystore
Java - Adding Certificate to the Java keystore
More like this
SeaLights Java Agent - Using the Sealights Java Proxy Server
SeaLights Java Agent - Using the Sealights Java Proxy Server
More like this
Java - SSL connection issue with java 7 under version 131
Java - SSL connection issue with java 7 under version 131
More like this
WebSphere - Error 404 (Page Not found) when enabling Sealights
WebSphere - Error 404 (Page Not found) when enabling Sealights
More like this
Java - SSL handshake failure to Sealights with Java 7
Java - SSL handshake failure to Sealights with Java 7
More like this