Upgrading and Migrating FTPS Connector to Version 2.0

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

Supported Upgrade Paths

From Version	To Version
1.8.x	2.0.x

From Version

To Version

1.8.x

2.0.x

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 and Configure Bouncy Castle Libraries and Security Provider. 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:

Application/Service	Version
Mule	4.3.0 and later

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:

In Anypoint Studio, create a Mule project.
In Mule Palette, click Search in Exchange.
In Add Dependencies to Project, enter FTPS in the search field.
In Available modules, select FTPS Connector and click Add.
Click Finish.
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:

In Studio, verify that there are no errors in the Problems or Console views.
Verify that there are no problems in the project pom.xml file.
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.