Course – LSS – NPI (cat=Spring Security)
announcement - icon

If you're working on a Spring Security (and especially an OAuth) implementation, definitely have a look at the Learn Spring Security course:


1. Introduction

This tutorial will focus on Login with Spring Security. We’re going to build on top of the previous Spring MVC example, as that’s a necessary part of setting up the web application along with the login mechanism.

Further reading:

Spring Security - Redirect to the Previous URL After Login

A short example of redirection after login in Spring Security

Two Login Pages with Spring Security

A quick and practical guide to configuring Spring Security with two separate login pages.

Spring Security Form Login

A Spring Login Example - How to Set Up a simple Login Form, a Basic Security XML Configuration and some more Advanced Configuration Techniques.

2. The Maven Dependencies

When working with Spring Boot, the spring-boot-starter-security starter will automatically include all dependencies, such as spring-security-core, spring-security-web, and spring-security-config among others:


If we don’t use Spring Boot, please see the Spring Security with Maven article, which describes how to add all required dependencies. Both standard spring-security-web and spring-security-config will be required.

3. Spring Security Java Configuration

Let’s start by creating a Spring Security configuration class that creates a SecurityFilterChain bean.

By adding @EnableWebSecurity, we get Spring Security and MVC integration support:

public class SecSecurityConfig {

    public InMemoryUserDetailsManager userDetailsService() {
        // InMemoryUserDetailsManager (see below)

    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        // http builder configurations for authorize requests and form login (see below)

In this example, we used in-memory authentication and defined three users.

Next we’ll go through the elements we used to create the form login configuration.

Let’s start by building our Authentication Manager.

3.1. InMemoryUserDetailsManager

The Authentication Provider is backed by a simple, in-memory implementation, InMemoryUserDetailsManager. This is useful for rapid prototyping when a full persistence mechanism is not yet necessary:

    public InMemoryUserDetailsManager userDetailsService() {
        UserDetails user1 = User.withUsername("user1")
        UserDetails user2 = User.withUsername("user2")
        UserDetails admin = User.withUsername("admin")
        return new InMemoryUserDetailsManager(user1, user2, admin);

Here we’ll configure three users with the username, password, and role hard-coded.

Starting with Spring 5, we also have to define a password encoder. In our example, we’ll use the BCryptPasswordEncoder:

public PasswordEncoder passwordEncoder() { 
    return new BCryptPasswordEncoder(); 

Next let’s configure the HttpSecurity.

3.2. Configuration to Authorize Requests

We’ll start by doing the necessary configurations to Authorize Requests.

Here we’re allowing anonymous access on /login so that users can authenticate. We’ll restrict /admin to ADMIN roles and securing everything else:

    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
            // ...

Note that the order of the antMatchers() elements is significant; the more specific rules need to come first, followed by the more general ones.

3.3. Configuration for Form Login

Next we’ll extend the above configuration for form login and logout:

public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
      // ...
      .defaultSuccessUrl("/homepage.html", true)
  • loginPage() – the custom login page
  • loginProcessingUrl() – the URL to submit the username and password to
  • defaultSuccessUrl() – the landing page after a successful login
  • failureUrl() – the landing page after an unsuccessful login
  • logoutUrl() – the custom logout

4. Add Spring Security to the Web Application

To use the above-defined Spring Security configuration, we need to attach it to the web application.

We’ll use the WebApplicationInitializer, so we don’t need to provide any web.xml:

public class AppInitializer implements WebApplicationInitializer {

    public void onStartup(ServletContext sc) {

        AnnotationConfigWebApplicationContext root = new AnnotationConfigWebApplicationContext();

        sc.addListener(new ContextLoaderListener(root));

        sc.addFilter("securityFilter", new DelegatingFilterProxy("springSecurityFilterChain"))
          .addMappingForUrlPatterns(null, false, "/*");

Note that this initializer isn’t necessary if we’re using a Spring Boot application. For more details on how the security configuration is loaded in Spring Boot, have a look at our article on Spring Boot security auto-configuration.

5. The Spring Security XML Configuration

Let’s also have a look at the corresponding XML configuration.

The overall project is using Java configuration, so we need to import the XML configuration file via a Java @Configuration class:

@ImportResource({ "classpath:webSecurityConfig.xml" })
public class SecSecurityConfig {
   public SecSecurityConfig() {

And the Spring Security XML Configuration, webSecurityConfig.xml:

<http use-expressions="true">
    <intercept-url pattern="/login*" access="isAnonymous()" />
    <intercept-url pattern="/**" access="isAuthenticated()"/>

    <form-login login-page='/login.html' 
      authentication-failure-url="/login.html?error=true" />
    <logout logout-success-url="/login.html" />

            <user name="user1" password="user1Pass" authorities="ROLE_USER" />
        <password-encoder ref="encoder" />

<beans:bean id="encoder" 

6. The web.xml

Before the introduction of Spring 4, we used to configure Spring Security in the web.xml; only an additional filter added to the standard Spring MVC web.xml:

<display-name>Spring Secured Application</display-name>

<!-- Spring MVC -->
<!-- ... -->

<!-- Spring Security -->

The filter – DelegatingFilterProxy – simply delegates to a Spring-managed bean – the FilterChainProxy – which itself is able to benefit from full Spring bean life-cycle management and such.

7. The Login Form

The login form page is going to be registered with Spring MVC using the straightforward mechanism to map views names to URLs. Furthermore, there is no need for an explicit controller in between:


This, of course, corresponds to the login.jsp:

   <form name='f' action="login" method='POST'>
            <td><input type='text' name='username' value=''></td>
            <td><input type='password' name='password' /></td>
            <td><input name="submit" type="submit" value="submit" /></td>

The Spring Login form has the following relevant artifacts:

  • login – the URL where the form is POSTed to trigger the authentication process
  • username – the username
  • password – the password

8. Further Configuring Spring Login

We briefly discussed a few configurations of the login mechanism when we introduced the Spring Security Configuration above. Now let’s go into some greater detail.

One reason to override most of the defaults in Spring Security is to hide that the application is secured with Spring Security. We also want to minimize the information a potential attacker knows about the application.

Fully configured, the login element looks like this:

public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {

Or the corresponding XML configuration:


8.1. The Login Page

Next we’ll configure a custom login page using the loginPage() method:


Similarly, we can use the XML configuration:


If we don’t specify this, Spring Security will generate a very basic Login Form at the /login URL.

8.2. The POST URL for Login

The default URL where the Spring Login will POST to trigger the authentication process is /login, which used to be /j_spring_security_check before Spring Security 4.

We can use the loginProcessingUrl method to override this URL:


We can also use the XML configuration:


By overriding this default URL, we’re concealing that the application is actually secured with Spring Security. This information should not be available externally.

8.3. The Landing Page on Success

After successfully logging in, we will be redirected to a page that by default is the root of the web application.

We can override this via the defaultSuccessUrl() method:


Or with XML configuration:


If the always-use-default-target attribute is set to true, then the user is always redirected to this page. If that attribute is set to false, then the user will be redirected to the previous page they wanted to visit before being prompted to authenticate.

8.4. The Landing Page on Failure

Similar to the Login Page, the Login Failure Page is autogenerated by Spring Security at /login?error by default.

To override this, we can use the failureUrl() method:


Or with XML:


9. Conclusion

In this Spring Login Example, we configured a simple authentication process. We also discussed the Spring Security Login Form, the Security Configuration, and some of the more advanced customizations available.

The implementation of this article can be found in the GitHub project – this is an Eclipse-based project, so it should be easy to import and run as it is.

When the project runs locally, the sample HTML can be accessed at:

Course – LSS (cat=Security/Spring Security)

I just announced the new Learn Spring Security course, including the full material focused on the new OAuth2 stack in Spring Security:

res – Security (video) (cat=Security/Spring Security)
Comments are open for 30 days after publishing a post. For any issues past this date, use the Contact form on the site.