AcegiSecurity Plugin - Implementation Overview

Added by Burt Beckwith, last edited by Burt Beckwith on Apr 30, 2008  (view change)

The Acegi plugin simplifies the work involved in integrating Spring Security (formerly called Acegi Security) into Grails applications. By combining a core configuration with user-specified options and overrides, it creates a best-practice configuration of Spring Security in any Grails application while allowing developers to make config changes without having to deal with the complexity of using Acegi directly.

Spring Security is a very powerful framework and is the default security framework for Spring, but this power comes at the cost of complexity and a rather steep learning curve. The Grails Acegi plugin manages most of the complexity for you while allowing application-specific customization.

By installing the plugin you get:

  • configuration of all Spring Security filters in web.xml via doWithWebDescriptor() and Spring beans via doWithSpring()
  • all required Spring Security jar files
  • Domain classes, Controllers, and CRUD GSPs for User and Role management and persistence
  • Login and Logout Controllers and GSPs
  • DefaultSecurityConfig.groovy with default attribute values, and SecurityConfig.groovy for application-specific overrides
  • Taglibs and Service for Security
  • User signup Controller and GSPs, including CAPTCHA support

History

  • April 30, 2008
    • released 0.3
  • April 15, 2008
    • released 0.2.1
  • Nov, 2007
    • added snapshot version of 0.2
  • May 5, 2007
    • upgraded to support latest Grails 0.5+
  • Mar 25, 2007
    • added fixed version for grails-0.5-SNAPSHOT - changed getController() to getArtefact("Controller", ControllerName ).
  • Feb 9, 2007
    • Fixed more for 0.4 release
    • name changed to 'AcegiSecurity Plugin' from 'Acegi on Grails Plugin'
  • Jan , 2007
    • Fixed to use sessionFactory
  • Dec 23, 2006
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.