Hi,
I'm still not satisfied with the options so far and I'm sure I do not fully
understand it:
Although the valve works in that I can set the principal on the catalina
request, realm.authenticate("username","credentials") within the valve is not
actually passing anything to my JAAS login modul
On 18/05/2010 15:42, Neville Peter wrote:
> The authentication will take place without any user intervention. For
> example, from a request parameter or cookie value.
>
> BTW, I have just managed to get it to work by using a custom Valve that
> extends AuthenticatorBase and uses my JAAS realm. T
The authentication will take place without any user intervention. For example,
from a request parameter or cookie value.
BTW, I have just managed to get it to work by using a custom Valve that extends
AuthenticatorBase and uses my JAAS realm. The valve adds the principal to the
request and this
On 18/05/2010 10:51, Neville Peter wrote:
> I need to login programmatically, but continue to support getRemoteUser().
>
> I have written a csutom JAAS login module (no callbackhandler required) and
> this can be seen to run when I programmatically logon within my filter
> servlet using:
> Logi
I need to login programmatically, but continue to support getRemoteUser().
I have written a csutom JAAS login module (no callbackhandler required) and
this can be seen to run when I programmatically logon within my filter
servlet using:
LoginContext lc = new LoginContext("MyJAASAccess",subject)
