No bean named 'springSecurityFilterChain' is defined | Baeldung
If the XML configuration is using the security namespace – as the example above, then declaring a simple <http> element will ensure that the filter bean is created and everything starts up correctly:
1 2 3 | <http auto-config='true'> <intercept-url pattern="/**" access="ROLE_USER" /></http> |
Another possible reason is that the security configuration is not imported at all into the overall context of the web application.
If the security XML config file is named springSecurityConfig.xml, make sure the resource is imported:
Read full article from No bean named 'springSecurityFilterChain' is defined | Baeldung
No comments:
Post a Comment