AppFuseSecurity

This is version 11. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

The purpose of this page is to describe what I did to integrate Acegi Security into 1.8. Hopefull you can use this to change your pre-1.8 applications to Acegi Security if you like. The nice thing about migrating to Acegi Security is your application becomes more portable and you don't have to worry about configuring your application server. Also, there weren't many code changes involved in the integration process - which proves Acegi Security works very well with all the existing code that talks to the security methods of the Servlet API (i.e. request.isUserInRole(), etc.)

Part II of this tutorial shows you how to remove Acegi Security from AppFuse and revert back to Container-Managed Authentication.

Table of Contents

• [1] Add Acegi Security JARs to your project
• [2] Create applicationContext-security.xml
• [3] Configure filters and filter-mappings
• [4] Remove web-security.xml from metadata/web
• [5] Add an "enabled" variable to the User object
• [6] Configure logging for Acegi Security
• [7] Remove setting from LoginServlet.java to prevent duplicate logins

Add Acegi Security JARs to your project [#1]

• acegi-security-0.7-SNAPSHOT.jar
• commons-codec.jar

Create applicationContext-security.xml [#2]

Configure filters and filter-mappings [#3]

Remove web-security.xml from metadata/web [#4]

Add an "enabled" variable to the User object [#5]

• Enable user as part of Signup Process
• Add "enabled" column to the sample-data.xml and enable all users
• Add key for enabled label to view and ResourceBundles

Configure logging for Acegi Security [#6]

Remove setting from LoginServlet.java to prevent duplicate logins [#7]