Certificates

Similar to HTTPS, but unlike SSH, FTPS servers may be required to provide a public key certificate. A certificate authority must sign this required certificate.

If it is not signed, some FTPS clients may generate a warning stating that the certificate is not valid. Whether to trust such a certificate is your choice.

The FTPS servers may optionally require the user to authenticate with a client certificate.

The client certificate typically needs to be signed by a certificate authority trusted by the server.

Supported client certificate file formats are:

• Personal Information Exchange – PCKS #12 (.pfx or .p12);
• Base64 encoded PEM X.509 (.pem or .key), either:
  • containing both the private key and the certificate;
  • containing a private key only, with the certificate in a separate file. The certificate needs to have the same base name as the private key, with .crt or .cer extensions, and be in the Base64 encoded PEM X.509 format or binary DER format.

Importing a certificate

1. Navigate to the Organization > Certificates page.

2. Click Import Certificate.

3. Drag and drop a valid certificate into the window.

4. Configure the following fields:

   • Certificate Name
   • Certificate Type
   • Pass Phrase (Optional)

5. Click Import.

caution

To use the MFT’s FTPS server endpoint with a client certificate, you must provide the certificate to MFT Support for adding certificate to the server's certificate store.