Skip to end of metadata
Go to start of metadata

Introduction

Jitterbit Harmony supports Transport Layer Security (TLS) 1.2 encryption, with limited backward compatibility with TLS 1.1 and TLS 1.0.

We recommend using TLS 1.2 with your endpoints where possible, as TLS 1.1 and TLS 1.0 are subject to security vulnerabilities and have been disabled in many systems.

In addition, using TLS 1.2 may be required in order to meet requirements for some endpoints. For example, starting in September 2019, Salesforce began disabling TLS 1.1 and requiring the TLS 1.2 version (see Salesforce Disabling TLS 1.1).

TIP: For additional details on how Jitterbit manages information security, see the Jitterbit Security and Architecture White Paper.

TLS Support in Jitterbit Applications

Jitterbit Harmony Cloud Agents and cloud-based Harmony applications accessed through the Jitterbit Harmony Portal already use TLS 1.2 automatically without user action. Cloud Agents 10.47 and higher no longer support TLS 1.0 and TLS 1.1 with JDBC driver connections to database endpoints in Cloud Studio (Database Connection) and Design Studio (Database Source and Database Target).

If you have an older version of a locally installed Jitterbit application, you may need to upgrade the version in order to use TLS 1.2. Later versions of some Jitterbit applications may no longer be backward compatible with TLS 1.1 or TLS 1.0, as noted below. To check the version you are currently using, see Finding My Jitterbit Version.

These are the minimum Jitterbit versions that support TLS 1.2 and instructions for upgrading: