[
https://issues.apache.org/jira/browse/WAGON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555021#comment-14555021
]
Dan Tran commented on WAGON-440:
--------------------------------
the correct solution is to allow api client to set its own
UIKeyboardInteractive, the way I can set it back to default implementation used
by Jcsh
> wagon-ssh not able to handle JSch interactive mode
> --------------------------------------------------
>
> Key: WAGON-440
> URL: https://issues.apache.org/jira/browse/WAGON-440
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Affects Versions: 2.9
> Reporter: Dan Tran
> Assignee: Dan Tran
> Fix For: 2.10
>
>
> JSch by default works with ssh interactive authentication programmatically (
> no user interaction). wagon-ssh does not honor this automation
> the work around is to use public key, and password authentication. For my
> case, our automation requires user/password. However, by default, most linux
> boxes now have password authentication disable by default
> a good reference to his issue is
> http://www.ganymed.ethz.ch/ssh2/FAQ.html#passwordauth . this also applies to
> jcsh
> I found a fix for this at AbstractJschWagon
> session.setPassword(ui.getPassword());
> //session.setUserInfo( ui );
> will need a more generic solution
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
