grails-plugins/grails-spring-security-kerberos — pull request #1 by selera (2011-10-20 21:05:45+00:00)
Title: 'Active' config flag for spring-security-kerberos

This change allows users to have the Kerberos plugin installed, but configured inactive. This is useful for when the different environments such as DEVT, vs PROD need to disable Kerberos. This change introduces a simple config switch which enables some flexibility in configuration per environment.

Looking at the conf options for the spring security plugins,the spring-security-ldap grails plugin has:
- a conf.ldap.active = true flag in its DefaultLDAPSecurity.groovy config file
- the plugin's doWithSpring closure examines this flag to determine whether to initialise/activate the plugin.

I've implemented the same approach for the spring-security-kerberos grails plugin (except we want conf.kerberos.active). This allows you to have the kerberos plugin installed into your application from a grails perspective, but allow the app's Config.groovy to control whether the plugin's beans are actually injected into SpringSecurity or not, (perhaps programmatically).

It fixes: http://jira.grails.org/browse/GPSPRINGSECURITYKERBEROS-3