Hi All, The endpoint of a interface has changed but the old certificate does not list this new endpoint and it is not possible to use the interface anymore. Therefore I am looking for a way to temporarily bypass the certificate check – SoapUI does not have issues to send test messages, so it should be possible somehow, right? com.mendix.core.CoreException: com.mendix.modules.microflowengine.MicroflowException: HTTP transport error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching [...] found. at [...][0 of 1] (CallWebservice : 'Call web service '[...]'') [...] I do not intend to run this in production, I would just like to go on with the development :) Thanks!
Lukas Tost - CLEVR
This can be done by setting the certificate the server provides as “valid” authority. To do this, you first need to download the (public) certificate, for example by browsing to the endpoint using a browser:
You can go to tab “Details” and then Export (I always choose .CER Base64 encoded).
Next step is to upload this certificate as Authority to your running appliction. I'm assuming you use the Mendix cloud, locally or on-premises it is somewhat different.
Go to the details of your environment, to the network-tab and scroll down to “Outgoing Connections Certificates” and click Add Authority.
Probably a restart is needed and now the certificate should be accepted to set-up a connection to that server.