The way I solved the issue was removing he user from the tomcat role table. Tomcat itself will then not allow you to login. I am using a Realm authentication as well. In the user table I specified what "role" the user had (either plain user, manager, admin, or a trainer), then based off of that, the tomcat role table was populated at "create new user" time. It will throw your 403 error (which mine does)
- Josh On Tue, Oct 20, 2009 at 7:18 PM, Nirvann <jatin.kulka...@yahoo.com> wrote: > > Sorry guys to have bothered you with my silly mistake. Actually, I had > configured 403 error page in web.xml file but the page was not at proper > location. Hence I was getting 404 file not found. Now I can access the role > error page for authorization error. Thanks a lot for all your insights. > > regards, > nirvan. > -- > View this message in context: > http://www.nabble.com/doubts-about-tomcat-form-based-authentication-tp25970503p25984106.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
