Hi,
+-From: Mick McLaughlin mclaughlin.m...@gmail.com --
|_Date: Fri, 23 Apr 2010 12:21:26 -0400 __
|
|I don't see how I can return null a 2nd time after getPassword() is called
|unless I hack it to detect if it's already been asked for.
That hack will be needed for
well actually no its not being invoked infinitely, however it is invoked
approx 35-40 times. FYI, in the testcase, the pass is correct but the user
is not...
On Fri, Apr 23, 2010 at 11:15 AM, Mick McLaughlin mclaughlin.m...@gmail.com
wrote:
yes it is! Should I be doing something to keep this
Hi,
+-From: Mick McLaughlin mclaughlin.m...@gmail.com --
|_Date: Fri, 23 Apr 2010 11:20:33 -0400 __
|
|well actually no its not being invoked infinitely, however it is invoked
|approx 35-40 times. FYI, in the testcase, the pass is correct but the user
|is not...
well my UserInfo implementation is just a stub class with setters and
getters for the hostname, user pass. The user does not receive a separate
prompt for the password. I.E. MyUserInfo info = new MyUserInfo(some
hostname, some user, some pass)
the method getPassword() returns this.pass which
Hello,
I am attempting to implement a timeout using session.connect(3). If a
user adds the wrong credentials, I want the connection to return an auth
fail JschException however, it seems to be ignoring this and finally returns
the exception after many minutes.
Part of my testcase looks like
Hi,
+-From: Mick McLaughlin mclaughlin.m...@gmail.com --
|_Date: Thu, 22 Apr 2010 16:58:04 -0400 __
|
|I am attempting to implement a timeout using session.connect(3). If a
|user adds the wrong credentials, I want the connection to return an auth
|fail
