[ http://mc4j.org/jira/browse/STS-102?page=all ]
Ben Gunter resolved STS-102.
----------------------------
Resolution: Won't Fix
Assignee: Ben Gunter (was: Tim Fennell)
This seems to work well as an add-on so I'll close this issue as Won't Fix.
> 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: Ben Gunter
> 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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
