Raible's Wiki
Raible Designs
Wiki Home
News
Recent Changes
AppFuse
Homepage- Korean
- Chinese
- Italian
- Japanese
QuickStart Guide
- Chinese
- French
- German
- Italian
- Korean
- Portuguese
- Spanish
- Japanese
User Guide
- Korean
- Chinese
Tutorials
- Chinese
- German
- Italian
- Korean
- Portuguese
- Spanish
Other Applications
Struts ResumeSecurity Example
Struts Menu
Set your name in
UserPreferences
UserPreferences
Referenced by
...nobody
JSPWiki v2.2.33
![[RSS]](https://raibledesigns.com/wiki/images/xml.png "Aggregate the RSS feed")
Hide Menu
AppFuseSecurity |
|
| Your trail: | |
Difference between version 30 and version 1:
| At line 1 changed 1 line. |
| [AppFuse] has used [container-managed security|http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/Security4.html#67530] since it was first created. However, in version 1.8, this was replaced with the [Acegi Security Framework for Spring|http://acegisecurity.sf.net]. The main reasons for this can be found on [raibledesigns.com|http://raibledesigns.com/page/rd?anchor=re_j2ee_app_server_security]. |
| This page is a starting point for [AppFuse] related security issues, tutorials and how to's. As of 1.8, AppFuse uses [Acegi Security|http://acegisecurity.sourceforge.net] for authentication and authorization. In 1.7 and prior, container-managed authentication (CMA) was used. You can revert to CMA if you prefer. |
| * How to migrate your pre-AppFuse 1.8 application to [use Acegi Security for authentication|AppFuseAuthentication]. |
| * How to use Acegi Security for [securing methods by role|AppFuseSecurityMethods]. |
| * How to use Acegi Security to [control access to objects with ACLs|AppFuseAcegiACL]. |
Back to AppFuseSecurity, or to the Page History.