The supported protocol for files on an FTP server (File Transfer Protocol) is FTPS (FTP with SSL/TSL) in explicit mode. File name is the URL of an FTP request that has a result in the corresponding file format (csv, xlsx, json, or xml). Format:
ftp://[<user>[:<password>]@]<host>[:<port>]/<url-path>
Examples:
ftp://ftp.heise.de/pub/INDEX
ftp://user001:secretpassword@private.ftp-servers.example.com/mydirectory/myfile.txt
| SSL mode | Off: SSL is not used.
Trust: SSL certificate will be imported to the keystore if not yet available. Verify: SSL certificate is verified. Note: if the certificate has not been imported correctly, the following error message occurs: “Unable to find valid certification path to requested target”. |
| User name | The username for the FTP request. |
| Password | The password for the FTP request. |
| Active mode | Active mode is not supported in Jedox Cloud. This option should remain unchecked (default). See note below for migrating from Jedox On-Prem. |
Note:
-
Current FTPS implementation does not allow for the reuse of TLS-session ID between control and data channel, which is forced by some servers for security reasons. This requirement has to be disabled on the FTPS server installation.
-
For FTP connections via VPN, a specific route must be created in the VPN configuration from the Cloud Console for each port used for data transfer.
Migrating FTP connections from Jedox On-Prem
When migrating an FTP location from an on-prem Jedox setup that has active mode checked, uncheck active mode and make sure the FTP server you want to connect to is configured to support passive mode. If the FTP server is behind a firewall, this might require configuring a dedicated port range in the FTP server, which must be configured on the firewall as well.
For private FTP servers (which require a dedicated VPN configuration in Cloud Console), in addition to routing to port 21, separate routes for each port in the configured range must be created as well. Select the number of ports in the configured port range, depending on your needs for parallel access.
If the FTP location is only used in a single standard execution, a single extra port (in addition to 21) might be enough. If you read / write from / to the FTP location in parallel, make sure to open enough ports to avoid blocking.
Updated December 18, 2024