If it really isn't possible to use the standard form login, a portable solution (across all 2.3 containers) would be a servlet filter that implement your own form login.
Another option that we implemented for jsp 1.0: Our application has one main page that contains the common parts of all pages and makes includes for the dynamic parts of the pages. This main page uses a user bean that performs the authentication. This is portable across all jsp versions. (Has the disadvantage that you can't protect static resources) This approach is also valid if you don't have the main page, you just have to define the bean in all pages. A variant of this approach is to use a controller servlet that catches all request and forward them to the requested resource or to a login form. > -----Urspr�ngliche Nachricht----- > Von: Bruno Antunes [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 3. Juli 2002 18:49 > An: Tomcat User List > Betreff: WebContainner Portable Login Module > > I am trying to implement a custom Login, that will work > regardless of the Web Container, that we are using. > I want a something more customized than the FORM authentication > defined in the Servlet 2.3 specification. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
