PaaS Partner Community

  • February 15, 2015

MFT – Setting up SFTP Transfers using Key-based Authentication by Shub Lahiri

Juergen Kress
PaaS Partner Adoption

Executive Overview

clip_image002MFT supports file transfers via SFTP. Often MFT customers receive a public key from their partners and want to use them to receive files via SFTP. This blog describes the setup required to enable such an MFT flow that would receive files from partners using key-based authentication.

MFT includes an embedded SFTP server. We will configure it with the supplied public key to receive files from remote partners. Upon receipt of a file, a simple MFT transfer will initiate and place the file in a pre-defined directory within the local filesystem.

Solution Approach


The overall solution consists of the following steps:

  • Generate public-private key pair on the remote machine and copy the public key to MFT server
  • Generate public-private key pair on the machine running MFT server
  • Import the private key from MFT machine in MFT keystore
  • Import the public key from partner machine in MFT keystore
  • Configure SFTP server with private key alias
  • Configure MFT users and corresponding SFTP directories to be used by remote partners
  • Enter SSH Keystore password
  • Restart embedded SFTP Server
  • Create Embedded SFTP Source
  • Create File Target
  • Create an MFT transfer using the above source and target
  • Deploy and Test
Task and Activity Details

The following sections will walk through the details of individual steps. The environment consists of the following machines:

  • VirtualBox image running MFT 12c on OEL6 (oel6vb)
  • Remote Linux machine used for initiating the transfer via SFTP client (slc08vby)
I. Generate public-private key pair on the remote machine and copy the public key to MFT server

To generate a private-public key pair, we use the command-line tool ssh-keygen. The tool creates 2 files for private and public key. For our purposes in this exercise, we will only be using the public key by copying it to the MFT machine from here. As a common practice, all the key files are saved in $HOME/.ssh directory. A transcript of a typical session is shown below. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.