In a phased approach, Salesforce began disabling TLS 1.0 encryption protocol to increase security. This change impacts K2 integration with Salesforce via the K2 Salesforce service broker. K2 has a fix available for supported K2 blackpearl versions (4.6.10, 4.6.11, and 4.7). This bulletin describes your options to ensure that your Salesforce-integrated K2 solutions continue to work.
You can disregard this bulletin if you do not integrate K2 solutions with Salesforce.
Last summer, Salesforce began disabling TLS 1.0 encryption support and, once complete in July 2017, will enforce TLS 1.1 or later. As the July 2017 end date approaches, you must update your K2 blackpearl environments to ensure that your Salesforce-integrated K2 solutions continue to work.
Read more about these Salesforce changes in their Knowledge Article.
To ensure your Salesforce-integrated K2 solutions continue to work past July 2017, you have a few options. They are:
There is a KB article (KB001764) available describing the error message you receive when using the unsupported TLS 1.0 encryption method. In addition, the product documentation describing the Salesforce integration configuration is updated with this information. Please contact your K2 Account Manager if you have any questions. K2 Product Team
Thank you for your submission. We will be in contact shortly to assist you.