Erik van Oosten wrote: > > Wicket supports per component authorisation. You could take a look at > wicket-auth-roles-example (a small project available through svn). > In this project some components (pages) are marked. The mark indicates > which roles are required for the component. As long as the user does not > hit those components the application runs fine. As soon as the user does > hit such a component, the sign-in page is displayed. > > Erik. >
Thanks for advice, example is good. But I have to use tomcat authentication (not authorization). To make it work I have to declare <security-constraint>. -- View this message in context: http://www.nabble.com/Authentication-Tomcat-%3C-%3E-Wicket-tf2588672.html#a7254648 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
