Skip to end of metadata
Go to start of metadata

IMPORTANT: Due to a Salesforce Change, You Must Upgrade Your Jitterbit Harmony Installation Now to Ensure TLS Version Compatibility

As a user of an older version of Jitterbit Harmony, you may be using the TLS 1.0 or TLS 1.1 version of encryption to connect with your Salesforce Org. Starting in September 2019, Salesforce will begin disabling the TLS 1.1 encryption protocol and require the TLS 1.2 version.

At Jitterbit, we pride ourselves on staying ahead of the curve and have already updated our software to support TLS 1.2 (with backward compatibility with the TLS 1.1 and TLS 1.0 versions). In order to continue using Jitterbit Harmony software in 2019 and beyond, you may need to upgrade to our latest release.

NOTE: The change in TLS version is being required by several software vendors, not just Salesforce. For example, Autodesk and NetSuite are taking similar measures. If you do not use those software packages, you may not need to upgrade at this time. However, we do recommend updating to the latest distribution as a best practice. Future versions of the software you use may require the upgrade.

Why is this happening?

To maintain the highest security standards, and promote the safety of your data, Jitterbit and our partners occasionally need to make security improvements and retire older encryption protocols. To maintain alignment with these best practices and updated compliance requirements from the PCI Security Standards Council, Salesforce will be disabling the use of TLS 1.1 for inbound and outbound connections to Salesforce. Other software vendors such as NetSuite and Autodesk are taking similar steps with upgrading their TLS versions.

Why is Salesforce disabling TLS 1.1 encryption protocol?

TLS 1.1 is no longer considered strong cryptography. To maintain the highest security standards and promote the safety of your data, Salesforce must disable the use of TLS 1.1 for connections to and from Salesforce. This is an industry-wide change and is not specific to Salesforce. Beginning in 2019, any websites using encryption protocols that need to follow PCI Security Standards will no longer allow TLS 1.1 connections. Please see these Salesforce pages for additional information:

What does this mean for me?

After Salesforce disables TLS 1.1 encryption, any systems connecting to Salesforce will need to use TLS 1.2 encryption or higher.  Systems attempting to connect to Salesforce using encryption protocols lower than TLS 1.2 will NOT be able to connect to Salesforce. This includes older versions of Jitterbit software. 

NOTE:  Newer versions of Jitterbit Harmony support TLS 1.2 and are backward compatible with TLS 1.1 and TLS 1.0.

When will Salesforce begin disabling TLS 1.1?

Starting in September 2019, Salesforce will begin disabling the use of TLS 1.1 for inbound and outbound connections using a phased approach. 

Salesforce will disable TLS 1.1 over a series of maintenance windows currently scheduled to occur between September 2019 and October 2019.

What action do I need to take?

In order to maintain seamless access to your Salesforce Org through Jitterbit, you need to upgrade to the latest version of Jitterbit by following the instructions at Jitterbit Harmony TLS Version Compatibility Upgrade.


On This Page

Related Topics

Last updated:  Aug 09, 2019