When no certificates are required for authentication
Follow the steps below if no certificates are required:
1. Add an FTPS Resource in GoAnywhere. Specify the parameters (host name, port, user ID, password, etc.) for the server. Do not specify any certificates for the Resource. This will instruct GoAnywhere to trust this FTPS server no matter what certificate is sent during the SSL handshake.
2. Add an FTPS task to a GoAnywhere Project and choose the FTPS Resource (created in step 1).
3. You will be able to send and receive files to/from that FTPS server by adding Put or Get elements to the FTPS task in the Project.
When certificates are required for authentication
Follow these steps if the FTPS server needs to authenticate your client certificate and/or if you need to authenticate the trading partner's certificate.
1. Follow these steps if your trading partner requires your public certificate for authenticating your client:
- a. Create a certificate in the Key Vault Certificate Manager.
- b. If your trading partner requires that your certificate is signed by a third party (not self-
signed), then follow the steps below:
- c. If your certificate was not signed by a third party (self-signed), then Export your Certificate
and send it to your trading partner.
- a. If your trading partner's certificate was not signed by a third party (self-signed), then request the public certificate from your trading partner.
b. Import their public certificate into the Key Vault.
c. If this is a certificate chain, where the certificate that signed your certificate was signed by another certificate and so on, then all certificates in the chain must be added to your Key Vault.
4. Add an FTPS task to a GoAnywhere Project and choose the FTPS Resource (created in step 3).
5. You will be able to send and receive files to/from that FTPS server by adding Put or Get elements to the FTPS task in the Project.
w. GoAnywhere.com | HelpSystems.com