Aha! I re-found the problem I was having. It turns out the function name is essential for Shiro to use your beans. For example, if you name your ShiroFilterChainDefinition bean anything other than "shiroFilterChainDefinition", the system won't use it in initialization.
This reminds me a bit of when Spring was XML-based, but I've not seen it much since the move to annotations. After all, the point of the @Bean annotation is to tell Spring that function creates a bean, and the return type is used to figure out what type of thing it provides. Anyway, I've uploaded a non-working example here: https://github.com/ry99/shiro-example <https://github.com/ry99/shiro-example> . The function "Config::improperlyNamedShiroFilterChainDefinition()" creates a DefaultShiroFilterChainDefinition that never gets used. I don't suppose this is a bug so much as a gotcha. I've included some details here for the next time I stumble upon this problem . It might be helpful if the documentation mentioned it, and also which things can be configured with beans. For example, I had to do some digging to figure out that "rememberMeManager()" was the function I needed to implement to disable remember-me. -- Sent from: http://shiro-user.582556.n2.nabble.com/
