Spring Security auto-configuration in Spring Boot - Mini Project: Build & Apply

Spring Security Auto-Configuration Setup

📖 Scenario: You are building a simple web application using Spring Boot. You want to secure your application with minimal setup by using Spring Security's auto-configuration feature.This will help you protect your web pages with a default login form and basic security settings without writing much code.

🎯 Goal: Set up Spring Security auto-configuration in a Spring Boot project to enable default security features.You will create the main application class, add a configuration property to customize security behavior, and verify the default security is applied.

📋 What You'll Learn

Create a Spring Boot main application class with @SpringBootApplication

Add a configuration property to disable CSRF protection

Use Spring Security auto-configuration without custom security classes

Add a simple REST controller to test security

💡 Why This Matters

🌍 Real World

Spring Security auto-configuration is commonly used to quickly secure web applications with sensible defaults, saving time and effort.

💼 Career

Understanding Spring Security auto-configuration is essential for Java developers working on secure web applications using Spring Boot.

1

Create the Spring Boot main application class

Create a class called SecurityAutoConfigApplication in package com.example.security with the @SpringBootApplication annotation and a main method that runs SpringApplication.run(SecurityAutoConfigApplication.class, args).

Spring Boot

package com.example.security;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class SecurityAutoConfigApplication {
    // Your code here
}

Hint

Use @SpringBootApplication on the class and add a main method that calls SpringApplication.run.

2

Add a configuration property to disable CSRF

In src/main/resources/application.properties, add the line spring.security.enable-csrf=false to disable CSRF protection in Spring Security auto-configuration.

Spring Boot

package com.example.security;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class SecurityAutoConfigApplication {
    public static void main(String[] args) {
        SpringApplication.run(SecurityAutoConfigApplication.class, args);
    }
}

# Add the property spring.security.enable-csrf=false in application.properties

Hint

Open application.properties and add spring.security.enable-csrf=false exactly.

3

Add a simple REST controller

Create a class called HelloController in package com.example.security with @RestController. Add a method hello() mapped to /hello that returns the string "Hello, secured world!".

Spring Boot

package com.example.security;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

// Your code here

Hint

Use @RestController on the class and @GetMapping("/hello") on the method returning the exact string.

4

Run the application with Spring Security auto-configuration

Ensure no custom security configuration classes exist. Run the application and verify that Spring Security auto-configuration applies default security with a login form and that CSRF is disabled as configured.

Spring Boot

// No custom security classes should be added
// Run the application and test security behavior
// Your code here

Hint

Do not add any security config classes. Run and check the default login page appears and CSRF is disabled.

Practice

1. What happens when you add spring-boot-starter-security to a Spring Boot project without any additional configuration?

easy

A. The application runs without any security restrictions.

B. All web endpoints are secured with a default login page.

C. Only REST endpoints are secured, web pages remain open.

D. The application throws an error due to missing configuration.

Solution

1. Step 1: Understand default behavior of spring-boot-starter-security

   Adding this starter enables Spring Security auto-configuration which secures all web endpoints by default.

2. Step 2: Recognize the default login page

   Spring Security provides a default login page automatically when no custom security config is provided.

3. Final Answer:

   All web endpoints are secured with a default login page. -> Option B

4. Quick Check:

   Default security = secured endpoints + login page [OK]

Hint: Default security locks all endpoints with login page [OK]

Common Mistakes:

• Thinking endpoints remain open without config
• Assuming only REST endpoints are secured
• Believing an error occurs without config

2. Which of the following is the correct way to disable Spring Security auto-configuration in a Spring Boot application?

easy

A. @Configuration(exclude = SecurityAutoConfiguration.class)

B. @EnableAutoConfiguration(exclude = SecurityAutoConfiguration.class)

C. @ComponentScan(exclude = SecurityAutoConfiguration.class)

D. @SpringBootApplication(exclude = SecurityAutoConfiguration.class)

Solution

1. Step 1: Identify the correct annotation to exclude auto-configuration

   Spring Boot allows excluding auto-configurations via the exclude attribute in @SpringBootApplication.

2. Step 2: Confirm the correct class to exclude

   The class to exclude for disabling security auto-configuration is SecurityAutoConfiguration.class.

3. Final Answer:

   @SpringBootApplication(exclude = SecurityAutoConfiguration.class) -> Option D

4. Quick Check:

   Disable auto-config = exclude in @SpringBootApplication [OK]

Hint: Exclude SecurityAutoConfiguration in @SpringBootApplication [OK]

Common Mistakes:

• Using @EnableAutoConfiguration instead of @SpringBootApplication
• Trying to exclude in @ComponentScan or @Configuration
• Not specifying the correct class to exclude

3. Given this Spring Boot application with spring-boot-starter-security added and no custom security config, what will happen when a user accesses /hello endpoint?

 @RestController
 public class HelloController {
   @GetMapping("/hello")
   public String hello() {
     return "Hello World";
   }
 }

medium

A. The user sees "Hello World" without login.

B. The endpoint returns 404 Not Found.

C. The user is redirected to a login page before seeing "Hello World".

D. The application throws a runtime exception.

Solution

1. Step 1: Recall default security behavior with no custom config

   All endpoints are secured and require authentication by default.

2. Step 2: Understand access flow to /hello endpoint

   Accessing /hello triggers Spring Security to redirect to the default login page before allowing access.

3. Final Answer:

   The user is redirected to a login page before seeing "Hello World". -> Option C

4. Quick Check:

   Default security = login redirect before access [OK]

Hint: No config means login page before any endpoint access [OK]

Common Mistakes:

• Assuming endpoints are open without login
• Expecting 404 error for existing endpoint
• Thinking runtime exception occurs

4. You added spring-boot-starter-security but your application fails to start with a bean creation error related to AuthenticationManager. What is the likely cause?

medium

A. You defined a custom SecurityFilterChain but forgot to expose an AuthenticationManager bean.

B. You did not add spring-boot-starter-web dependency.

C. You excluded SecurityAutoConfiguration but still use security annotations.

D. You have multiple @SpringBootApplication classes.

Solution

1. Step 1: Understand the error context with AuthenticationManager bean

   When customizing security by defining a SecurityFilterChain, Spring Boot no longer auto-configures AuthenticationManager.

2. Step 2: Identify missing bean definition

   You must manually expose an AuthenticationManager bean to satisfy dependencies.

3. Final Answer:

   You defined a custom SecurityFilterChain but forgot to expose an AuthenticationManager bean. -> Option A

4. Quick Check:

   Custom filter chain needs AuthenticationManager bean [OK]

Hint: Custom SecurityFilterChain requires AuthenticationManager bean [OK]

Common Mistakes:

• Blaming missing web dependency
• Ignoring need for AuthenticationManager bean
• Assuming multiple @SpringBootApplication causes this error

5. You want to customize Spring Security auto-configuration to allow public access to /public/** endpoints but secure all others with form login. Which configuration snippet correctly achieves this?

hard

A. Define a SecurityFilterChain bean with http.authorizeHttpRequests().requestMatchers("/public/**").permitAll().anyRequest().authenticated().and().formLogin().

B. Exclude SecurityAutoConfiguration and manually configure WebSecurityConfigurerAdapter to permit /public/**.

C. Add @EnableWebSecurity and override configure(HttpSecurity http) to permit /public/** and disable form login.

D. Add @SpringBootApplication(exclude = SecurityAutoConfiguration.class) and use http.csrf().disable().

Solution

1. Step 1: Use SecurityFilterChain bean to customize security rules

   Spring Security 5.7+ recommends defining a SecurityFilterChain bean for custom rules.

2. Step 2: Permit /public/** and require authentication for others with form login

   The method chain authorizeHttpRequests().requestMatchers("/public/**").permitAll().anyRequest().authenticated().and().formLogin() correctly sets these rules.

3. Final Answer:

   Define a SecurityFilterChain bean with http.authorizeHttpRequests().requestMatchers("/public/**").permitAll().anyRequest().authenticated().and().formLogin() -> Option A

4. Quick Check:

   Permit public paths + secure others + form login = Define a SecurityFilterChain bean with http.authorizeHttpRequests().requestMatchers("/public/**").permitAll().anyRequest().authenticated().and().formLogin(). [OK]

Hint: Use SecurityFilterChain bean with permitAll and formLogin [OK]

Common Mistakes:

• Excluding auto-config and using deprecated WebSecurityConfigurerAdapter
• Disabling form login when it is required
• Misusing @EnableWebSecurity without proper bean