Salesforce Certificate Changes in Early 2018
Salesforce has recently published a news release that is relevant to all users of middleware solutions.
To uphold the best practices in Security, Salesforce has decided to rotate some certificates out during January and February 2018. Google Chrome no longer supports Symantec-issued HTTPS certifications and is now going to use DigiCert-issued certificates instead.
This could have an impact if you and your company use a middleware solution like Mulesoft, Scribe, IBM Broker, etc. to interact with Salesforce once the certificates are updated by Salesforce. According to Salesforce, “To test your software and middleware solutions, use //certtest.force.com as the base URL of the API login URL.
- If you see an invalid username error or a different HTTP status code, then the test was successful.
- If you see a certificate trust error, then the trust was unsuccessful.”
For the vast majority of Salesforce users this will have no impact on your day-to-day experience. However, companies with middleware solutions are most likely going to require some configuration updates to trust the new root, intermediate, and other relevant certificates with DigiCert.
The deployment schedule for these updates certificates are: 1) Sandbox instances during the second week of January, and 2) Production instances during the second week of February. Additional information can be found at the following site, Salesforce Certificates change from Symantec to Digicert in Jan 2018. These updates should be thoroughly tested and validated in your Sandbox instances prior to the Production deployment.
If you would like to see what CleanSlate can do for you and your Salesforce Sales and Service Cloud orgs please contact us today!