I went completely mad chasing why on earth an admin server was starting with weblogic.security.SSL.ignoreHostnameVerification=false, even if all the possible places (startWebLogic.sh, startup.properties in the data/nodemanager folder...) I had specified -Dweblogic.security.SSL.ignoreHostnameVerification=true.
After hours, I found out that I forgot to set the Hostname Verification to "None" (in server/SSL/advanced), it was instead the BEA Hostname Verifier
in WLST:
cd("/Servers/" + serverName + "/SSL/" + serverName )
set( 'HostnameVerificationIgnored', 1 )
Unless you turn it off, in some cases you can get the dreaded BEA-090482 BAD_CERTIFICATE alert .
After hours, I found out that I forgot to set the Hostname Verification to "None" (in server/SSL/advanced), it was instead the BEA Hostname Verifier
in WLST:
cd("/Servers/" + serverName + "/SSL/" + serverName )
set( 'HostnameVerificationIgnored', 1 )
Unless you turn it off, in some cases you can get the dreaded BEA-090482 BAD_CERTIFICATE alert .