tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: API for user authentication
Date Mon, 11 Nov 2002 08:12:36 GMT
It will bind you forever to a particular Tomcat version, but the following
should work:

The authenticating Servlet can't be protected, so that servlet saves off the
Principal as a special session variable.  You then write a (Context level)
Valve & Realm. The Valve looks for the special session varaible, and if
found, calls setUserPrincipal on the HttpRequest with the value.  Now, the
FormAuthenticator will say that you are already authenticated.  The Realm
can then check against any required roles to allow you access to your
protected pages.

----- Original Message -----
From: "Johann Uhrmann" <johann.uhrmann@xpecto.com>
To: <tomcat-dev@jakarta.apache.org>
Sent: Sunday, November 10, 2002 2:57 AM
Subject: API for user authentication


> Hi,
>
> as far as I know, there is only one possible way to use form based
> authentication with Tomcat:
>
> - sending a request to a restricted site
> - getting the login form instead
> - logging in and getting the restricted site
>
>
> However, the following scenario seems more common in web applications:
>
> - having a welcome page that offers a user name and
>   password field
> - after submitting that form the user gets the index page
>   of the web application
>
> It seems to me that there is no way to provide the second scenario with
> tomcat. Therefore, I ask You whether there is an API call that can
> verify a username/password combination and create a user session.
>
> That kind of api call would be handy in the second scenario as the index
> page could easily check the given user/pass and send a redirect to the
> error page if it was wrong or show up the index page if the login
> succeeded.
>
> I know that this kind of functionality could be simulated by
> implementing a proprietary login mechanism. However, that would mean to
> throw away the security-constraint mechanisms (web.xml), the built-in
> user verification (jdbc-realm, ldap,...) and would require every site to
> check whether the user is logged in or not.
>
> If there is no API call to verify user/password then please treat this
> message as a feature request.
>
>
> Thank You very much,
>
> Johann Uhrmann
>
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-dev-help@jakarta.apache.org>
>


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


Mime
View raw message