Creating FTPS Profiles

FTP Secure works over an SSL or secure socket layer protocol which also supports security and authentication functionality using a user ID, password, and authentication certificates. These certificates must be up to date and the system checks the viability of the certificates before allowing the transfer.

Note: To work with the set up of FTP and SFTP, you need an advanced understanding of how to move files between devices over a network. The setup involves a knowledge of the servers involved, the ports, and access to those areas. The data requirements for set up in Eclipse are typical for this method of transferring files.

To create an FTPS profile:

  1. From the Tools menu, select Communication Profile Maintenance.

  2. In the Profile/New field, type new.

Note: If you want to edit a current profile, enter the profile name and select Edit.

  1. At the prompt, enter the new name you want to use.

  2. In the Type field, select FTPS and click Edit.

Field

Description

Server

The server name from which or to which you want to use to transmit files.

Important: Do NOT include the website protocol, such as ftp://, or the port number in this field.

Port

The port name on the server.

The default is 990.

Directory

The directory where transmitted files should be extracted from or deposited to. By default, the system uses the root directory of the FTPS site.

Use Passive

Indicate if you want to use:

  • Passive - FTP connections originate from the client only and the server can be configured to restrict the range of ports used. This setting is generally preferred since the serve can be configured to permit the connections through its firewall.

  • Active - FTP connections occur from both the client and server during FTP. These connections can sometimes be blocked by firewalls which do not allow outbound connections to clients.

File Name*

The standard file name to be used when transmitting files. While optional, this field can be used to define a default file name for when this profile is used.

User

The user name on the server.

Password

The password for the server.

CA Cert Path

The path to a trusted certificate authority certificate used to validate the remote server's certificate.

Client Cert Path*

The path for the client certificate.

Client Key Path*

The path to the client public key to share with your partner.

Client Key Pass*

The password required to access the local client key.

*Optional

  1. Use the Test button to test the connection and ensure the credentials are correct.

  2. Save your changes and exit the window.