> It's a bug. Line 118 of ShiroGrailsPlugin.groovy should read:
>
> authenticationStrategy =
> application.config.security.shiro.authentication.strategy
>
> In other words, the "modularAuthenticationStrategy" property was
> renamed to "authenticationStrategy".
I'm going to change the way this works. Setting the strategy via
Config.groovy effectively bypasses the standard Spring configuration
mechanism, which isn't a great idea in my view. Instead, you will be
able to provide your own bean configuration for
"shiroAuthenticationStrategy" in either resources.groovy or
resources.xml. This has the added benefit that dependent plugins can
easily provide their own defaults (think of the Nimble plugin).
In other words, you'll be able to add something like:
beans = {
shiroAuthenticationStrategy(org.apache.shiro.authc.pam.AtLeastOneSuccessfulStrategy)
}
to resources.groovy.
One other thing: I may make AtLeastOneSuccessfulStrategy the default
for the plugin. If you have more than one realm, I'm convinced it's
the more common strategy to use.
Cheers,
Peter
