Disable SSL check for a specific integration using midserver

lucas-mesquita
Tera Contributor

yesterday

Hello guys! I have a specific requirement of integrating Service Now event management module to vRealize. 

 

Thing is, it uses a SelfSigned Certificate and even thought I've imported all the hosts certificates to the midserver, communication is still not possible, with the following outcome:

 

org.apache.commons.httpclient.HttpException: java.security.cert.CertificateException: No subject alternative DNS name matching <server> found

 

As there is some complexity in changing all vRealize hosts certificates with it, I would like to take a more simple approach, as for now it is still in proof of concept phase.

 

Whilst it is done, would it be possible to disable SSL validation specifically to that integration? 

0 Helpfuls
  • 100 Views
1 REPLY 1

Matthew_13
Mega Sage

yesterday

Yes, this is a common issue with vRealize integrations, and what you’re seeing makes sense.

The key point is that this error is not just about a self-signed certificate being untrusted. The message
No subject alternative DNS name matching <server> found means the certificate presented by vRealize does not contain the hostname you are connecting to in its SAN field. Importing the cert into the MID Server trust store fixes trust, but it does not bypass hostname/SAN validation.

Regarding your question about disabling SSL validation:

  • There is no clean, out-of-the-box way to disable SSL validation for only one integration.

  • You can disable hostname verification using a system property (commonly used during PoCs), but this is a global change, not scoped just to vRealize.

The commonly used workaround is:

  • Disable hostname verification at the platform/MID HTTP client level

This will allow the connection to succeed, but it applies broadly and should be treated as PoC-only, not something to leave in place long term.

The best and supported fix, even for a PoC, is to:

  • Either connect using a hostname that already exists in the certificate’s SAN, or

  • Regenerate the vRealize certificate to include the correct DNS name (or IP) in SAN

So in short:

  • Yes, you can bypass SSL checks, but it’s global, not integration-specific

  • Importing certs alone won’t fix SAN mismatches

  • Correcting the SAN on the vRealize cert is the cleanest and safest solution

@lucas-mesquita - Please mark Solution Accepted and Thumbs Up if you find Helpful

0 Helpfuls