I'm having a similar issue since upgrading to 4.6.4. The hostname of the site hosting the WSDL is a.b.com.au whereas the server certificate is *.b.com.au, so technically it does not match and browsers complain, etc. but prior to SoapUI 4.6.4 it did not care about this mismatch. As of 4.6.4 I can no longer update the definition of my service and receive an InvalidDefinitionException in SoapUI and in the error log I see the following:
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching a.b.c.com.au found.
Is there any way to get this to work, or am I going to have to download the WSDL outside of SoapUI and then update from the saved file?
Regards,
Dave