Why input validation is critical in Spring Boot - See It in Action

Why Input Validation is Critical in Spring Boot

📖 Scenario: You are building a simple Spring Boot web application that accepts user data through a form. To keep the app safe and reliable, you need to check the user input carefully.

🎯 Goal: Learn how to add input validation in a Spring Boot controller to protect your app from bad or harmful data.

📋 What You'll Learn

Create a simple data class to hold user input

Add a validation configuration variable

Use Spring Boot validation annotations in the controller

Complete the controller method to handle validation results

💡 Why This Matters

🌍 Real World

Web applications often receive data from users. Validating this data prevents errors and security problems.

💼 Career

Understanding input validation is essential for backend developers to build secure and robust applications.

1

Create a User Data Class

Create a class called User with two fields: String name and String email. Use standard Java syntax for the class and fields.

Spring Boot

// Create the User class with name and email fields
// Your code here

Hint

Define a simple Java class with private fields and public getter and setter methods.

2

Add Validation Annotations

Add validation annotations to the name and email fields in the User class. Use @NotBlank for name and @Email and @NotBlank for email. Import the annotations from jakarta.validation.constraints.

Spring Boot

import jakarta.validation.constraints.Email;
import jakarta.validation.constraints.NotBlank;

public class User {
    // Add @NotBlank to name
    private String name;
    // Add @Email and @NotBlank to email
    private String email;

    public User() {}

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public String getEmail() {
        return email;
    }

    public void setEmail(String email) {
        this.email = email;
    }
}

Hint

Use @NotBlank to ensure the field is not empty and @Email to check email format.

3

Create a Controller with Validation

Create a Spring Boot controller class called UserController. Add a method createUser that accepts a @Valid @RequestBody User user and a BindingResult result. Use @PostMapping("/users") on the method.

Spring Boot

import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RestController;
import jakarta.validation.Valid;
import org.springframework.validation.BindingResult;

@RestController
public class UserController {
    // Create createUser method with @PostMapping("/users")
    // Accept @Valid @RequestBody User user and BindingResult result
    // Your code here
}

Hint

Use @RestController on the class and @PostMapping on the method. Add @Valid and BindingResult parameters.

4

Handle Validation Results in Controller

In the createUser method, check if result.hasErrors() is true. If yes, return the string "Invalid input". Otherwise, return "User created".

Spring Boot

import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RestController;
import jakarta.validation.Valid;
import org.springframework.validation.BindingResult;

@RestController
public class UserController {
    @PostMapping("/users")
    public String createUser(@Valid @RequestBody User user, BindingResult result) {
        // Check if result has errors
        // Return "Invalid input" if errors exist
        // Otherwise return "User created"
        // Your code here
    }
}

Hint

Use result.hasErrors() to check validation and return the correct message.

Practice

1. Why is input validation critical in a Spring Boot application?

easy

A. It helps prevent invalid or harmful data from entering the system.

B. It makes the application run faster by skipping checks.

C. It automatically fixes user mistakes without notifying them.

D. It allows users to enter any data without restrictions.

Solution

1. Step 1: Understand the purpose of input validation

   Input validation ensures that data coming from users meets expected rules and formats.

2. Step 2: Identify the benefit in Spring Boot context

   This prevents harmful or incorrect data from causing errors or security issues in the app.

3. Final Answer:

   It helps prevent invalid or harmful data from entering the system. -> Option A

4. Quick Check:

   Input validation = prevent bad data [OK]

Hint: Input validation stops bad data before it breaks things [OK]

Common Mistakes:

• Thinking validation speeds up app by skipping checks
• Believing validation fixes user errors silently
• Assuming validation allows all data without limits

2. Which annotation is used in Spring Boot to ensure a field is not null during input validation?

easy

A. @Email

B. @Valid

C. @Size

D. @NotNull

Solution

1. Step 1: Recall common validation annotations

   @NotNull ensures a field must have a value and cannot be null.

2. Step 2: Differentiate from other annotations

   @Email checks email format, @Size checks length, and @Valid triggers validation on nested objects.

3. Final Answer:

   @NotNull -> Option D

4. Quick Check:

   @NotNull = no null allowed [OK]

Hint: Use @NotNull to block empty fields [OK]

Common Mistakes:

• Confusing @Email with @NotNull
• Using @Valid instead of @NotNull for null checks
• Thinking @Size checks for null values

3. Given this Spring Boot controller method snippet:

@PostMapping("/register")
public ResponseEntity<String> registerUser(@Valid @RequestBody User user) {
    return ResponseEntity.ok("User registered");
}

What happens if the user object has an invalid email format and @Email is used on the email field?

medium

A. The server crashes with an exception.

B. The method runs normally and registers the user.

C. Spring Boot returns a 400 Bad Request error automatically.

D. The invalid email is saved without error.

Solution

1. Step 1: Understand @Valid and @Email behavior

   @Valid triggers validation on the User object, and @Email checks the email format.

2. Step 2: Identify Spring Boot's response to validation failure

   If validation fails, Spring Boot automatically returns a 400 Bad Request response without running the method body.

3. Final Answer:

   Spring Boot returns a 400 Bad Request error automatically. -> Option C

4. Quick Check:

   Invalid input = 400 error [OK]

Hint: Invalid input with @Valid triggers 400 error [OK]

Common Mistakes:

• Assuming method runs despite invalid input
• Thinking server crashes instead of handling error
• Believing invalid data is saved silently

4. Consider this code snippet in a Spring Boot app:

public class User {
    @NotNull
    private String name;

    @Email
    private String email;

    // getters and setters
}

Why might the validation fail even if the user provides a valid email and name?

medium

A. Because the controller method is missing the @Valid annotation on the User parameter.

B. Because @NotNull does not check for empty strings.

C. Because @Email only works on numbers, not strings.

D. Because getters and setters are not annotated.

Solution

1. Step 1: Check validation trigger in Spring Boot

   Validation annotations like @NotNull and @Email require @Valid on the controller method parameter to activate validation.

2. Step 2: Understand why validation might not run

   If @Valid is missing, Spring Boot skips validation even if annotations exist on fields.

3. Final Answer:

   Because the controller method is missing the @Valid annotation on the User parameter. -> Option A

4. Quick Check:

   Missing @Valid means no validation [OK]

Hint: Always add @Valid on input parameters to trigger validation [OK]

Common Mistakes:

• Thinking @NotNull checks empty strings
• Believing @Email works on numbers
• Assuming getters/setters need annotations

5. You want to ensure a user's password is at least 8 characters and not null in a Spring Boot app. Which combination of annotations on the password field is best to enforce this?

hard

A. @Email @NotNull

B. @NotNull @Size(min = 8)

C. @Valid @NotEmpty

D. @Size(max = 8) @NotNull

Solution

1. Step 1: Identify annotations for null and length checks

   @NotNull ensures the password is not null, and @Size(min = 8) enforces minimum length of 8 characters.

2. Step 2: Eliminate incorrect options

   @Email is for emails, not passwords; @NotEmpty is similar but less strict than @NotNull; @Size(max = 8) limits max length, not minimum.

3. Final Answer:

   @NotNull @Size(min = 8) -> Option B

4. Quick Check:

   Not null + min length = @NotNull @Size(min=8) [OK]

Hint: Use @NotNull with @Size(min=8) for password rules [OK]

Common Mistakes:

• Using @Email for password validation
• Confusing max length with min length
• Skipping @NotNull and allowing null passwords