This is an advisory post for those customers who have written custom integrations against our Web Services API using one of our provided Rest Toolkits. On July 16, 2018 at 10:00 am MDT we will deprecate support of TLS 1.0 and 1.1 which may require that you take steps below to ensure that your custom integrations continue to work. The impacts to the Rest Toolkits are listed below. For additional information on TLS 1.0/1.1 Deprecation, see this community post.
No issues present in 3.1.1 or above versions. The early 3.1 and 2.x versions will fail to connect with an exception message similar to the following:
The request was aborted: Could not create SSL/TLS secure channel.
- Upgrade to .NET toolkit version 3.1.1 or above (recommended)
- Continue using 2.x version, but patch with code
- Minimum .NET framework version for TLS 1.2 support is 4.5
- Explicitly set the supported security protocols:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
Microsoft has also published a best practices guide on this topic: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls
Rally Rest Toolkit for Ruby
Has issues if used with a version of Ruby prior to 2.2.x only on Windows platforms.
No known issues with Ruby 2.2.x or 2.3.x or 2.4.x.
Work Item Connectors
Many of the Work Item Connectors need to be updated. Work Item Connectors that experience problems and need updating will return “tlsv1 alert protocol version” error.
For more information on the Connectors that need updating, see this community post.
App SDK 1.x/2.x
No known issues.
Please ensure you are using Java 1.8. Java 1.7 support TLS 1.2, but it is not enabled by default. You will need to enable the support for TLS 1.2 in case you are using Java 1.7.
No known issues.
Python 3.5 and 3.6 have no known issues.