Here we’ll discuss how we can log into the MFT Gateway SFTP server from WinSCP SFTP Client29 Dec 2021 by Kumudika Rupasinghe
As we already discussed how we can log into MFT Gateway SFTP server from FileZilla SFTP client, here we’ll discuss how we can log into the MFT Gateway SFTP server from WinSCP SFTP Client.
First, enable SFTP integration from the SFTP Integration view in MFT Gateway and download the private key file in PPK/PKCS1 format.
Note: If you are planning to use a PKCS1 file generated by MFT Gateway, make sure the file is not password-protected. Otherwise, you’ll get an error message; unsupported cipher, while converting the file into PuTTY format.
Then, open the pre-installed WinSCP client.
The Login dialog will appear automatically on startup, by default. If not, in the WinSCP client interface, open New Session from the navigation bar Session tab.
In the Login dialog, select New Site node in the tree on the left to configure a new session.
Then in the Session section, set the configuration details as below.
Fill the Username field with the username which you have provided when integrating SFTP in MFT Gateway.
Then click Advanced… and click Authentication under SSH in Advanced Site Settings. Then under Authentication parameters, browse for the private key file downloaded in Step 1 and upload it. If you select a PKCS1 formatted key file, a dialog box will pop up as shown below (if not, skip to Step 9). In this dialog box, WinSCP is asking to convert the private key file to the format it expects. Click OK to continue.
When WinSCP proceeds to convert the private key file, it will prompt for a name and a location to save the converted file. Provide a name and a location to continue. Then, a dialog box will pop up as shown below. Click OK to continue.
Click OK on Advanced Site Settings dialog box to continue.
Then click on the Login button in Login dialog.
If all goes well, you will be connected to the MFT Gateway SFTP server.
Once successfully logged in to your own SFTP space, you can find a directory listing as below, which correspond to different aspects of your AS2 message flow.