Configuring FTPS exchanges

About FTPS connections

Before you continue

Configuring Gateway as FTPS server with anonymous SSL (responder)

Configuring Gateway as FTPS client with anonymous SSL (initiator)

Configuring Gateway as FTPS server with client SSL (responder)

Configuring Gateway as FTPS client with client SSL (initiator)

About FTPS connections

FTPS is standard FTP that is secured over SSL. There are two modes of SSL authentication and two modes of SSL.

Authentication modes:

• SSL anonymous: The server is the only party that has a certificate and ensures that the data received from the server is genuine.
• Client SSL: Both the server and client have certificates which ensure that the client data received by the server is also genuine. The client security can be mandatory, optional or forbidden based on the TLS security profile defined in the Gateway Server.

Working in Gateway, in the TLS Security profile you can specify whether client authentication is mandatory, optional or forbidden.

SSL modes::

• Explicit: An FTPS client must explicitly request security from an FTPS server and then employ a mutually agreed encryption method.
• Implicit: An FTPS client is expected to challenge the FTPS server with a TLS/SSL ClientHello message. If such a message is not received by the FTPS server, the server drops the connection. Implicit SSL is considered to be a deprecated method of negotiating TLS/SSL for FTP. Implicit SSL is not defined in RFC 4217.

It is recommended that you avoid the use of implicit SSL. No RFC exists for this mode, so its implementation can vary. For the same reason, Axway can only guarantee that implicit SSL will be compatible when exchanges are from Gateway to Gateway.

Before you continue...

Make sure you have completed the common configuration tasks described in the dedicated topic:

View common task procedures

Configuring Gateway as FTPS server with anonymous SSL (responder)

In Gateway

Step	Task	Go to procedure
1	Activate the FTP protocol
2	Create a TLS Profile: Server FTPS_in
3	Create a Network Profile for the FTPS exchange and attach the TLS Profile
4	Create a Virtual File Directory for FTP

In PassPort

Step	Task	Go to procedure
1	Add the FTP protocol to the Remote Partner object

Configuring Gateway as FTPS client with anonymous SSL (initiator)

In PassPort

Step	Task	Go to procedure
1	Import the remote trading partner's public certificate

In Gateway

Step	Task	Go to procedure
1	Activate the FTP protocol
2	Create a Network Profile for the FTP exchange

In PassPort

Step	Task	Go to procedure
1	Add the FTP protocol to the Remote Partner object

In Gateway

Step	Task	Go to procedure
1	Configure the outbound connection
2	Test the outbound connection

Configuring Gateway FTPS server (responder) with client SSL

In PassPort

Step	Task	Go to procedure
1	Import the remote trading partner's public certificate

In Gateway

Step	Task	Go to procedure
1	Activate the FTP protocol
2	Create a TLS Profile: Server FTPS_ in
3	Create a Network Profile for the FTP exchange and attach the TLS Profile
4	Create a Virtual File Directory for FTP

In PassPort

Step	Task	Go to procedure
1	Add the FTP protocol to the Remote Partner object

Configuring Gateway an FTPS client with client SSL (initiator)

In PassPort

Step	Task	Go to procedure
1	Import the remote trading partner's public certificate

In Gateway

Step	Task	Go to procedure
1	Activate the FTP protocol
2	Create a Network Profile for the FTP exchange

In PassPort

Step	Task	Go to procedure
1	Add the FTP protocol to the Remote Partner object

In Gateway

Step	Task	Go to procedure
1	Configure the outbound connection
2	Test the outbound connection