[Patch] immediate usage of j_username and j_password in form at login time

[Jeff Tulley <JT...@novell.com>]

When another web application wants to do a seamless login to another
secured context, one option is to submit a form that contains the
"j_username" and "j_password" form values.  This patch checks if these
exist before doing a redirect to the login page, and if they do, it
attempts authentication.  Upon success, execution proceeds onto the
orginally-requested page as if the user had already been logged in at
the time of the request.

I see no issues with committing such a thing to Tomcat 4.1.x, but I may
be missing something.

Thanks,

Jeff Tulley  (jtulley@novell.com)
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

Re: [Patch] immediate usage of j_username and j_password in form at login time

[Remy Maucherat <re...@apache.org>]

Jeff Tulley wrote:
> When another web application wants to do a seamless login to another
> secured context, one option is to submit a form that contains the
> "j_username" and "j_password" form values.  This patch checks if these
> exist before doing a redirect to the login page, and if they do, it
> attempts authentication.  Upon success, execution proceeds onto the
> orginally-requested page as if the user had already been logged in at
> the time of the request.
> 
> I see no issues with committing such a thing to Tomcat 4.1.x, but I may
> be missing something.

Isn't that a proprietary feature ? I see why it can be useful though.

Remy


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org