camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-4506) The SFTP component: the keyboard-interactive auth method support
Date Wed, 12 Oct 2011 04:37:11 GMT


Daniel Kulp updated CAMEL-4506:

    Fix Version/s: 2.8.2
> The SFTP component: the keyboard-interactive auth method support 
> -----------------------------------------------------------------
>                 Key: CAMEL-4506
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ftp
>    Affects Versions: 2.8.1
>            Reporter: Eugene Kiselev
>            Assignee: Hadrian Zbarcea
>            Priority: Minor
>             Fix For: 2.8.2, 2.9.0
>         Attachments:
> As it was discussed in this topic
> The SFTP component may be slightly improved to support the keyboard-interactive auth
method and the compression,
> Preamble:
> It appeared that our sftp share we get files from doesn't support the ssh password auth
method and we're not allowed to put the public key to there. So the only ssh auth method we
can use is the keyboard-interactive. Unfortunately the SFTP camel component doesn't support
> However this can be easily fixed simply by providing the Jsch session with both the 
com.jcraft.jsch.UserInfo and com.jcraft.jsch.UIKeyboardInteractive interfaces. The UIKeyboardInteractive
has the only one promptKeyboardInteractive method which returns String[] containing the password
entered by user interactively. In our case I simply return a password.
> The implementation example is attached.
> Also it's sometime required to set the ssh compression to be able to process longsize
files. The compression fix is also implemented in the attached file. Compression requires
the zlib jar to be in the pom.
> This was tested with the 0.1.44-1 version of the jsch and the 1.0.7 version of the jzlib.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message