Bird
Raised Fist0
Spring Bootframework~5 mins

Stateless authentication mental model in Spring Boot

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

Stateless authentication lets a server check who you are without saving your info between requests. This makes apps faster and easier to scale.

When building APIs that many users access at the same time.
When you want to avoid storing user sessions on the server.
When you want your app to work well across multiple servers or cloud instances.
When you want simpler server design without session management.
When you want users to stay logged in without server memory.
Syntax
Spring Boot
1. Client sends login info to server.
2. Server verifies and creates a token (like JWT).
3. Server sends token back to client.
4. Client sends token with each request in headers.
5. Server checks token to allow or deny access.

The token usually contains user info and expiry time.

Server does not keep any session data; it trusts the token.

Examples
User logs in and receives a token to use later.
Spring Boot
POST /login
Request Body: {"username": "user", "password": "pass"}
Response: {"token": "eyJhbGciOiJI..."}
Client sends token in header to get protected data.
Spring Boot
GET /profile
Headers: Authorization: Bearer eyJhbGciOiJI...
Response: {"name": "User", "email": "user@example.com"}
Sample Program

This simple Spring Boot app shows stateless auth. The login returns a token string. The profile endpoint checks the token in the Authorization header. No session is stored on the server.

Spring Boot
package com.example.demo;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.web.bind.annotation.*;
import jakarta.servlet.http.HttpServletRequest;

@SpringBootApplication
@RestController
public class DemoApplication {

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

    // Simulate login endpoint
    @PostMapping("/login")
    public String login(@RequestParam String username, @RequestParam String password) {
        if ("user".equals(username) && "pass".equals(password)) {
            // In real app, create JWT token here
            return "token12345"; // simple token for demo
        }
        return "Invalid credentials";
    }

    // Protected endpoint
    @GetMapping("/profile")
    public String profile(HttpServletRequest request) {
        String authHeader = request.getHeader("Authorization");
        if (authHeader != null && authHeader.equals("Bearer token12345")) {
            return "{\"name\": \"User\", \"email\": \"user@example.com\"}";
        }
        return "Unauthorized";
    }
}
OutputSuccess
Important Notes

Tokens should be signed and encrypted in real apps for security.

Tokens usually expire after some time to reduce risk.

Always send tokens over HTTPS to keep them safe.

Summary

Stateless authentication uses tokens to identify users without server memory.

Clients send tokens with each request to prove who they are.

This method helps apps scale and stay simple.

Practice

(1/5)
1. What is the main idea behind stateless authentication in Spring Boot?
easy
A. The server does not keep user session data; clients send tokens each time.
B. The server stores all user sessions in memory for quick access.
C. The server uses cookies to remember users between requests.
D. The server requires users to log in for every single request manually.

Solution

  1. Step 1: Understand stateless authentication concept

    Stateless means the server does not save any user session data between requests.
  2. Step 2: Identify how user identity is maintained

    Clients send a token with each request to prove who they are without server memory.
  3. Final Answer:

    The server does not keep user session data; clients send tokens each time. -> Option A
  4. Quick Check:

    Stateless = No server session, token sent each time [OK]
Hint: Stateless means no server memory, token sent every request [OK]
Common Mistakes:
  • Thinking server stores session data
  • Confusing cookies with stateless tokens
  • Assuming login required every request
2. Which of the following is the correct way to send a token in a stateless Spring Boot API request?
easy
A. Include the token in the request body as plain text.
B. Send the token in the Authorization header as a Bearer token.
C. Store the token in a server-side session variable.
D. Attach the token as a URL query parameter without encoding.

Solution

  1. Step 1: Recall token transmission best practice

    Tokens are usually sent in the Authorization header using the Bearer scheme.
  2. Step 2: Eliminate incorrect methods

    Request body is not standard for tokens; server-side session breaks statelessness; URL query parameters are insecure and not recommended.
  3. Final Answer:

    Send the token in the Authorization header as a Bearer token. -> Option B
  4. Quick Check:

    Token in Authorization header = correct [OK]
Hint: Tokens go in Authorization header as Bearer [OK]
Common Mistakes:
  • Putting token in request body
  • Using server session storage
  • Sending token in URL query insecurely
3. Given this Spring Boot controller snippet using stateless authentication:
@GetMapping("/profile")
public ResponseEntity<String> getProfile(@RequestHeader("Authorization") String authHeader) {
    if (authHeader == null || !authHeader.startsWith("Bearer ")) {
        return ResponseEntity.status(401).body("Unauthorized");
    }
    String token = authHeader.substring(7);
    if (token.equals("valid-token")) {
        return ResponseEntity.ok("User Profile Data");
    } else {
        return ResponseEntity.status(403).body("Forbidden");
    }
}

What will be the response if the client sends header Authorization: Bearer valid-token?
medium
A. 401 Unauthorized
B. 403 Forbidden
C. 200 OK with 'User Profile Data'
D. 500 Internal Server Error

Solution

  1. Step 1: Check Authorization header presence and format

    The header is present and starts with "Bearer ", so it passes the first check.
  2. Step 2: Extract token and compare

    The token extracted is "valid-token", which matches the expected valid token.
  3. Step 3: Determine response

    Since token is valid, the method returns 200 OK with "User Profile Data".
  4. Final Answer:

    200 OK with 'User Profile Data' -> Option C
  5. Quick Check:

    Valid token = 200 OK response [OK]
Hint: Valid Bearer token returns 200 OK [OK]
Common Mistakes:
  • Confusing 401 and 403 status codes
  • Ignoring token prefix check
  • Assuming server stores session
4. Identify the bug in this stateless authentication filter code snippet:
public boolean isValidToken(String token) {
    if (token == null || token.isEmpty()) {
        return false;
    }
    // Token validation logic
    return token.equals("valid-token");
}

public void doFilter(HttpServletRequest req, HttpServletResponse res) {
    String auth = req.getHeader("Authorization");
    if (auth != null && auth.startsWith("Bearer ")) {
        String token = auth.substring(7);
        if (!isValidToken(token)) {
            res.setStatus(401);
        }
    }
    // Continue filter chain
}

What is the main issue?
medium
A. Possible NullPointerException if Authorization header is missing
B. Token validation logic is incorrect
C. Response status code should be 403 instead of 401
D. Filter does not extract token correctly

Solution

  1. Step 1: Analyze header usage

    The original code calls auth.startsWith("Bearer ") without checking if auth is null.
  2. Step 2: Identify risk

    If Authorization header is missing, auth is null, so calling startsWith causes NullPointerException.
  3. Final Answer:

    Possible NullPointerException if Authorization header is missing -> Option A
  4. Quick Check:

    Check null before startsWith to avoid error [OK]
Hint: Check for null before calling startsWith [OK]
Common Mistakes:
  • Assuming header always present
  • Mixing 401 and 403 status codes
  • Ignoring null safety in Java
5. In a stateless Spring Boot app using JWT tokens, which approach best supports scaling across multiple servers?
hard
A. Store user sessions in a shared database accessed by all servers.
B. Cache user sessions in server memory for faster access.
C. Use sticky sessions to keep users on the same server.
D. Validate JWT tokens on each request without server session storage.

Solution

  1. Step 1: Understand stateless scaling needs

    Scaling means any server can handle any request without shared session state.
  2. Step 2: Evaluate options

    Storing sessions in DB or memory adds state and complexity; sticky sessions tie users to one server, limiting scaling.
  3. Step 3: Identify best stateless method

    Validating JWT tokens on each request keeps servers stateless and allows easy scaling.
  4. Final Answer:

    Validate JWT tokens on each request without server session storage. -> Option D
  5. Quick Check:

    Stateless + JWT = validate token each request [OK]
Hint: Stateless scaling means no server session, validate tokens each time [OK]
Common Mistakes:
  • Using sticky sessions limits scaling
  • Storing sessions breaks statelessness
  • Caching sessions in memory causes sync issues