Hi geeks,
Most of you would have seen this email from ServiceNow with the subject "SSL certificate notification: Be informed"
Anyhow pasting the content of the email below.
SSL certificate notification
Be informed • No downtime • March 2024 We like to keep things secure. So, twice a year we update the SSL certificate supporting your ServiceNow instances in our data centers. The last update was performed in September 2023. Here's what you can expect - This is a change to the *.service-now.com SSL certificate only. It will not affect the Entrust Root Certificate Authority, which does not expire until 2030.
- If your organization does not hard-code SSL certificates, this update will not affect your ability to connect to your instance, and no action is needed from you.
- If you have hard-coded our leaf certificate into your infrastructure, you will need to manually update the certificate. Here are some common cases where hard-coded SSL certificates may be found:
- You use a proxy server to access your ServiceNow instance. The proxy may have the current SSL leaf certificate hard-coded into the proxy software.
- You have inbound integrations that connect to your ServiceNow instance. Some examples of these can be found here: ServiceNow Product Documentation: List of Available Integrations
|
| |
My Question is - I just want to know which kind of inbound integrations are those where one would hardcode the TLS/leaf certificate? Why would one do it, whats the purpose of it? Is it alternate to credentials? Do people still use it today?
