This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am developing an application using form-based uthorization in Tomcat 4.0.3. (My basic problem is that I want to log out, but until then I have another problem first..) In my web.xml I have defined the login page: <login-config> <auth-method>FORM</auth-method> <form-login-config> <form-login-page>/login.jsp</form-login-page> <form-error-page>/loginError.jsp</form-error-page> </form-login-config> </login-config>
The login page basically consist of the standard <form name="loginForm" method="POST" action="j_security_check"> <input type="text" name="j_username"> <input type="password" name="j_password"> <input type="submit" value="Login Now"> </form> It all works fine. When I try to access web-resource-collections protected by a security-constraint in web.xml I get redirected to login.jsp. But if I go to login.jsp directly I get this strange behavior: When entering correct user/pwd I get the error message "Apache Tomcat/4.0.3 - HTTP Status 400 - Invalid direct reference to form login page". But when entering an incorrect user/pwd I get send to the loginError.jsp page. Which means that at least the user/pwd get checked. So can I or can't I link directly to the login.jsp page and perform a login? Any ideas? /Steffen
Steffen Foldager<p>Sun Certified Java Programmer<br />Sun Certified Web Component Developer
You can't simply point a browser at the login page because there's no way to tell it where to got next! The login page's action is a builtin process, not a servlet or JSP that could then move you along to the next page. The idea behind the login facility is that since a user can jump into any part of a webapp that has a distinct URL, thus bypassing a login page, the whole login process is moved external to the webapp so that if someone addresses the webapp and they are not yet logged in, the original URL is intercepted, the login form is presented, and if (and ONLY if) the login succeeds will the original URL be presented. I also discovered to my pain that in Tomcat, a login form containing page-external references (such as CSS links) loses that saved URL, so it's best to keep the login page plain.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Mar 22, 2001
Thanks Tim. That is a good reason why the authorization is happening outside the web application, I didn't think of that. But still it doesn't solve my initial problem: I want to be able to log out. Without closing the browser which is currently my only option. /Steffen
2003? That goes beyond "resurrecting a zombie" right into reincarnation!
This is caused by directly refering to the login URL. Instead, you should go to a protected resource, such as Main.jsp. If login is required, this will redirect you to the login page. The "j_security_check" URL is a kind of temporary resource that only exists.if the tomcat decided that the login page should be shown.
For example -
if the protected resource is main.jsp
Then you should not specify the login.jsp in <welcome-file-list> in web.xml, instead you should specify the main.jsp.