Do we need to setup certificates when setting up MID server?

maxj · ‎04-20-2016

Our Infrastructure department setup a MID server to connect to our ServiceNow instance in order to link to SCOM. I am planning to use the MID server for sending outbound SOAP requests from ServiceNow to web services inside our network.

I noticed that even though the MID server connects to the servicenow instance via port 443, the department did not setup the certificates for SSL communications as it is optional. Does this mean that the communications between ServiceNow instance and the MID server is un-encrypted?

tstocking · ‎04-20-2016

The communication between the ServiceNow Instance and the MID Server is encrypted using SSL. The communication between your local hosts and the MID server may or may not be encrypted based on your configuration. For instance, LDAP traffic uses port 389 and is not secured. We changed it to LDAP-S using port 636 and had to install a Cert into the MID Server certificate store to secure traffic.

View solution in original post

tstocking · ‎04-13-2018

Our certs were set to expire a few weeks ago so I revisited this. However, we are no longer importing the cert into the certstore but somehow LDAP-S is still working as expected.

J_Sukhsagar · ‎05-10-2016

Hello Max,

As mentioned by Todd, the communication between the ServiceNow Instance and the MID Server is encrypted using SSL.

If you enable an SSL connection, you can set value with the com.glide.ssl.read.timeout system property. Entering a value in this field, however, overrides the value set in the property

Follow the Link provided by Tod and this one for better understanding:

LDAP Integration Setup - ServiceNow Wiki

Regards,

Sukhsagar

PS: Hit like, Helpful or Correct depending on the impact of the response

maxj · ‎05-11-2016

Thanks, Sukhsagar.