---
schema_version: "1"
id: 5c7079f7dea028d2d05705f88b30493801478ebb90f18e5cfa8df418eefb8e7e
title: Upgrading and Migrating FTPS Connector to Version 2.0
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/ftps-connector/2.0/ftps-connector-upgrade-guide.md
canonical_url: https://docs.mulesoft.com/ftps-connector/2.0/ftps-connector-upgrade-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7e24e4ca0ef1debcdf6d15e213b99c8ab77bf36d4a62e2675e18ef019bff7b5e
description: MuleSoft Documentation Site
release: "2.0"
latest: false
---
---
product: FTPS Connector
version: 2.0
---

# Upgrading and Migrating FTPS Connector to Version 2.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Upgrade Anypoint Connector for FTPS (FTPS Connector) to version 2.x.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>1.8.x</p></div></div></td><td><div><div><p>2.0.x</p></div></div></td></tr></tbody></table>

## Changes in This Release

This release contains the following changes:

- This connector is now compatible with Java 17.

- This connector is now FIPS 140-2 compliant.

- This connector no longer uses reflection to reuse the SSL session from the command channel to data
  channels. Instead, it now supports SSL session resumption between the client and host by using
  externally provided Bouncy Castle libraries which are to be set as top security providers. You can
  add these libraries with the new **Required Libraries** field in the connection type. For more
  information, refer to
  [Configure Java JDK for Session Reuse](https://docs.mulesoft.com/ftps-connector/2.0/ftps-studio-configuration#configure-java) and
  [Configure Bouncy Castle Libraries and Security Provider](https://docs.mulesoft.com/ftps-connector/2.0/ftps-studio-configuration#bouncycastle).
  Because Bouncy Castle security providers are required for running FTPS on Java 17, all Mule
  applications within the same JVM must adhere to its stricter cryptographic policies. This includes
  enforcing modern key sizes, secure algorithms, and updated TLS configurations—affecting keystores,
  truststores, and all TLS-based connectors.

- The `mule-file-commons` module dependency is removed.

- The **List** operation now returns the file path instead of the file content.

## Requirements

Ensure that you meet these requirements before you perform the upgrade:

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><div><div><p>Mule</p></div></div></td><td><div><div><p>4.3.0 and later</p></div></div></td></tr></tbody></table>

## Limitations

Before you perform the upgrade, be aware of these known limitations:

- Session reuse doesn’t work well with TLS 1.3 in CloudHub (same as with previous versions of FTPS
  Connector).

- The security providers are hardcoded, which means all Mule applications running on the same Java
  Virtual Machine (JVM) will share these security settings.

  Bouncy Castle security providers enforce stricter cryptographic policies and reject weak
  keystores, including those using weak algorithms (such as `SHA1withRSA`) or self-signed
  certificates. This affects all keystores in the JVM, even those not directly used by FTPS
  Connector. Ensure all keystores in your Mule applications meet modern security standards before
  upgrading.

## Upgrade Prerequisites

Before you perform the upgrade, complete these tasks:

- Create a backup of your files, data, and configurations in case you need to restore them.

- Validate all keystores across Mule applications on the same JVM. Replace any keystores using weak
  algorithms, such as `SHA1withRSA`, because Bouncy Castle rejects them.

## Upgrade Steps

Follow these steps to perform the upgrade:

1.  In Anypoint Studio, create a Mule project.

2.  In **Mule Palette**, click **Search in Exchange**.

3.  In **Add Dependencies to Project**, enter `FTPS` in the search field.

4.  In **Available modules**, select **FTPS Connector** and click **Add**.

5.  Click **Finish**.

6.  Verify that the FTPS Connector `mule-ftps-connector` dependency version is the one you are
    upgrading to in the `pom.xml` file in the Mule project.

Studio upgrades the connector automatically.

### Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.

2.  Verify that there are no problems in the project `pom.xml` file.

3.  Test the connection to verify that the operations work.

### Reverting the Upgrade

If it is necessary to revert to the previous version of FTPS Connector, change the
`mule-ftps-connector` dependency version in the project’s `pom.xml` file to the previous version.
You must update the project’s `pom.xml` file in Anypoint Studio.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)