[ http://mc4j.org/jira/browse/STS-102?page=comments#action_10646 ] Kai Grabfelder commented on STS-102: ------------------------------------
I this this one can be closed, as the security mechanism as described in the wiki is quite complete in my opinion. > Security Annotation > ------------------- > > Key: STS-102 > URL: http://mc4j.org/jira/browse/STS-102 > Project: Stripes > Issue Type: New Feature > Components: ActionBean Dispatching > Reporter: Nic Holbrook > Assigned To: Tim Fennell > Attachments: DispatcherServlet.java, DispatcherServlet.patch, > DispatcherServlet.patch, Secure.java, Secure.patch, > StripesAuthorizationException.java, StripesSecurityManager.java > > > I didn't see anything in the documentation relating to security. I was > thinking that with the annotations, it would be easy to implement a role > based security model for each of the action classes. We would just need a > security interface to implement and we could set it up something like this. > @Secure(role="users, powerusers", securityProvider="com.my.security.Provider") > This way, we would handle the security and the methods or action itself could > be locked down. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://mc4j.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
