Thanks for the feedback. I just stumbled upon the following issue in Grails, so it looks like its a known thing:
http://jira.codehaus.org/browse/GRAILS-5234 I noticed that the filter mapping for the ShiroFilter didn't have the ERROR dispatcher set, so I tried setting it, but it didn't seem to make a difference. <filter> <filter-name>securityContextFilter</filter-name> <filter-class>org.apache.shiro.spring.SpringShiroFilter</filter-class> <init-param> <param-name>securityManagerBeanName</param-name> <param-value>shiroSecurityManagerProxy</param-value> </init-param> </filter> <filter-mapping> <filter-name>securityContextFilter</filter-name> <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>ERROR</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping> I'll just follow up with the issue tracker and see if they have made any progress. Regards, Javid -- View this message in context: http://n2.nabble.com/Issue-with-Grails-Shiro-tp4568683p4569367.html Sent from the Shiro User mailing list archive at Nabble.com.
