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

maxj
Tera Contributor

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?

1 ACCEPTED SOLUTION

tstocking
Tera Guru

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

7 REPLIES 7

tstocking
Tera Guru

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.


tstocking
Tera Guru

For instructions on how to install the cert, check out here:   http://wiki.servicenow.com/index.php?title=MID_Server_Configuration#Adding_SSL_Certificates


maxj
Tera Contributor

Thank you Todd for your reply.   So the certificates are meant to secure communications between the local services and the MID server.   It was confusing while going through the their documentation.



Thanks!


@tstocking-

Is there any other config needed other than the instructions outlined above? I've updated the cacerts file but logs show no sign of a cert being passed