Thank you David. The solution worked. :)
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 8:51 PM
To: user@geronimo.apache.org
Subject: Re: handling JAAS callbacks
On Jun 13, 2006, at 11:32 PM, Sunny Saxena wrote:
> Aaron,
>
>
:49 PM
To: user@geronimo.apache.org
Subject: Re: handling JAAS callbacks
So it sounds like right now your JAAS lookup is going through a
Geronimo
login module, whether you like it or not. The
DecouplingCallbackHandler
is Geronimo's way of gathering all the input it needs in order to
M
To: user@geronimo.apache.org
Subject: Re: handling JAAS callbacks
So it sounds like right now your JAAS lookup is going through a Geronimo
login module, whether you like it or not. The DecouplingCallbackHandler
is Geronimo's way of gathering all the input it needs in order to
populate the various login m
or,
I suppose.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
Mulder
Sent: Monday, June 12, 2006 5:49 PM
To: user@geronimo.apache.org
Subject: Re: handling JAAS callbacks
So it sounds like right now your JAAS lookup is going through a Geronimo
So it sounds like right now your JAAS lookup is going through a
Geronimo login module, whether you like it or not. The
DecouplingCallbackHandler is Geronimo's way of gathering all the input
it needs in order to populate the various login modules that may be
configured for that security realm. (S
heya,
My application uses JAAS Login Modules for authentication.
I have created a gbean in my geronimo-application.xml specifying the loginmodule
in it.
Now, at the point in my application, where the authentication takes
place, the loginmodule class is found, but I get the following
er
