Please note that on June 1, 2018, SpringCM will disable the TLS 1.1 encryption protocol. After we disable TLS 1.1, any inbound or outbound connection with SpringCM will need to use the TLS 1.2 encryption protocol.
This change impacts all methods of communicating with the SpringCM platform:
- Access via internet browser
- Access via API integration (inbound and outbound / call out)
You and your users should not experience an impact accessing SpringCM in your browser(s) unless you are using a non-supported browser or you have disabled the supported encryption protocols in the browser.
To quickly test your browser compatibility, you can visit the SpringCM test site, which has TLS 1.1 disabled.
If you are able to view the site without errors, access to SpringCM via your browser should not be impacted by this change.
If you see a web page that includes the following text "Your browser is successfully negotiating with TLS 1.2," then your web browser is already compatible with SpringCM's scheduled TLS 1.1 deactivation on June 1, 2018.
If you experience errors, please refer to the compatibility guidelines posted in our corresponding Knowledge Article.
If you have additional questions or need help, please contact SpringCM Customer Support (firstname.lastname@example.org).
Thank you for your attention.