Skip to main content

FTPS

File Transfer Protocol Secure (FTPS) is an extension of the standard FTP protocol that adds support for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) cryptographic protocols. FTP(S) is widely used for secure business-to-business file exchanges, providing encryption for both authentication credentials and data transfers. Unlike SFTP, which operates over SSH, FTP(S) extends the traditional FTP protocol by layering security

FTP(S) supports three encryption modes:

  1. Explicit FTPS (FTPES)
  2. Implicit FTPS
  3. None (Standard FTP)

The FTP(S) process involves several key steps:

  1. Connection Initiation: The client initiates a TCP connection to the server (usually on port 21 for control, with additional ports for data transfer).
  2. TLS/SSL Negotiation: The client and server negotiate encryption algorithms and establish a secure connection (either implicit or explicit Encryption Mode).
  3. Certificate Exchange: The server presents its SSL/TLS certificate, which the client verifies against trusted certificate authorities.
  4. Authentication: The client authenticates using a username and password over the encrypted control channel.
  5. FTP(S) Transfers: A separate encrypted channel is established for file transfers, securing both commands and data. The client begins file operations.

UDMG FTP(S) Implementation​

UDMG's role in FTP(S) communications is determined by the Endpoint types used in your Pipeline configuration. UDMG can act as the FTP(S) Server or the FTP(S) Client. This flexibility allows UDMG to integrate with various partner scenarios: whether your partner exchanges files with you (UDMG as server) using their FTPS client, or you need to exchange files with them (partner's external FTP(S) server), using UDMG as the client.

This allows UDMG to interoperate with partners regardless of whether they must send or receive files, while supporting both unencrypted FTP and Explicit FTPS (FTPES).

UDMG as FTP(S) Server​

This configuration involves a UDMG as FTP(S) Server Pipeline.

UDMG as FTP(S) Server Diagram

In this configuration:

  1. UDMG hosts and operates the Local FTP Server Endpoint.
  2. External partners connect to UDMG using an FTP or FTPS client.
  3. Partners manage files and folders.
  4. Files are saved to a filesystem (defined in the Local Filesystem Endpoint).

UDMG as FTP(S) Client​

This configuration scenario involves a UDMG as FTP(S) Client (Push Scenario) Pipeline, where UDMG sends files from the local filesystem to an external FTP(S) server.

UDMG as FTP(S) Client Diagram - Push Scenario

In this configuration scenario:

  1. UDMG has access to a filesystem (defined in a Local Filesystem Endpoint).
  2. UDMG sends the file to your partner's server, defined in the Remote FTPS Server Endpoint.