With the PCI Security Standards Council's move to Transport Layer Security (TLS) 1.2 on the 30th of June, 2018, various 3rd-party providers are disabling the use of older TLS and SSL protocol versions in their products.
K2 integrates with many 3rd-party providers such as Microsoft SharePoint, DocuSign, and SalesForce. With the PCI move to TLS 1.2, when a K2 solution is integrated with any of these providers, and the system in which K2 resides is NOT configured for TLS 1.2, possible communication errors may occur.
K2 follows the Transport Layer Security (TLS) best practices with the .NET Framework (Microsoft), and does not specify a TLS or SSL version. K2 runs under the .Net 4.6 runtime, which fully supports TLS 1.2, for both server (inbound) and client (outbound) connections.
If the server on which K2 is installed is not correctly configured for TLS 1.2, errors may occur. Below is an example of an error that may occur when TLS 1.2 is not configured correctly:
The underlying connection was closed. An unexpected error occurred on a send.
In order to avoid these issues you have two options:
To implement the minimum requirement, add or edit the following keys in your K2 server's registry.
To implement the maximum protection for all .NET apps on the K2 server, including K2, add or edit the following keys in your K2 server's registry.