No bean named ‘springSecurityFilterChain’ is defined

1. The Problem

This article discusses a Spring Security configuration problem – the application bootstrapping process throwing the following exception:

SEVERE: Exception starting filter springSecurityFilterChain
No bean named 'springSecurityFilterChain' is defined

2. The Cause

The cause of this exception is straightforward – Spring Security looks for a bean named springSecurityFilterChain (by default), and cannot find it. This bean is required by the main Spring Security Filter – the DelegatingFilterProxy – defined in the web.xml:


This is just a proxy that delegates all its logic to the springSecurityFilterChain bean.

3. The Solution

The most common reason this bean is missing from the context is that the security XML configuration has no <http> element defined:

<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns="" 


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:

<http auto-config='true'>
    <intercept-url pattern="/**" access="ROLE_USER" />

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:


Or in XML:

<import resource="classpath:springSecurityConfig.xml" />

Finally, the default name of the filter bean can be changed in the web.xml – usually to use an existing Filter with Spring Security:


4. Conclusion

This article discusses a very specific Spring Security problem – the missing filter chain bean – and shows the solutions to this common issue.

I usually post about Security on Google+ - you can follow me there:

Get My 3 Spring eBooks
Download the 3 eBooks - Build Your App "The Right Way"
Build Web App with Spring (and prototype it to 90% very quickly)

, ,

  • Amit Singh

    Hi Baeldung, I have basic question. I am trying to implement spring security, but I am not sure which class should I use for custom authentication. User and role information are stored in database. I override Authentication manager class and used my custom login dao to fetch data from database. Most of suggesations i see is using “UserdetailService” can you please explain which one is better and why ? Thanx for help in advance.

    • baeldung

      If your users and credentials are stored in the database, then you don’t need to override the Authentication Manager or the Authentication Provider – you can simply provide a UserDetailsService and you’re done. It’s only for more complex scenarios that you would need to have your own provider or manager. Hope that clears things up.
      Thanks. Eugen.

      • Amit Singh

        Can I use Digest Authentication if I customize Authentication manager ? if yes how please provide some hint.

        • baeldung

          Thanks for the interesting feedback – I would suggest checking out the Spring Security Digest Authentication post for details about how to configure Digest Authentication. Also, it would be great if you could add comments in the relevant article – for example, a question about Digest auth belongs in that particular article.

          Thanks. Eugen.