Actually Step 3 should be this to accomodate those who do not have a
passphrase on their private key:
if (getConfiguration().getSftpPrivateKeyFile() != null &&
!getConfiguration().getSftpPrivateKeyFile().equals(""))
{
if (getConfiguration().getSftpPrivateKeyFilePassphrase() != null
&& !getConfiguration().getSftpPrivateKeyFilePassphrase().equals(""))
{
jsch.addIdentity(getConfiguration().getSftpPrivateKeyFile(),
getConfiguration().getSftpPrivateKeyFilePassphrase());
}
else
{
jsch.addIdentity(getConfiguration().getSftpPrivateKeyFile());
}
}
Should also mention that the private key file that I had was in openSSH
format, I can test with a private key in SSH.com format at a later time as
well. Putty-gen was used to generate all private/public key files and
Globscape Secure FTP server was the SFTP server.
--
View this message in context:
http://www.nabble.com/SFTP-Component-private-key---passphrase-for-connection-tp20711040s22882p20711165.html
Sent from the Camel - Development mailing list archive at Nabble.com.
