Why JWT matters for APIs in Spring Boot - Quick Recap

Recall & Review

beginner

What does JWT stand for and what is its main purpose in APIs?

JWT stands for JSON Web Token. It is mainly used to securely transmit information between parties as a JSON object, often for authentication and authorization in APIs.

intermediate

How does JWT improve security in API communication?

JWT improves security by allowing the server to verify the token's signature, ensuring the data is not tampered with and confirming the user's identity without storing session data on the server.

intermediate

Why is JWT considered stateless and why is this beneficial for APIs?

JWT is stateless because all user information is stored inside the token itself, so the server does not need to keep session data. This makes APIs scalable and easier to manage.

beginner

What are the three parts of a JWT?

A JWT has three parts separated by dots: Header (describes the token type and algorithm), Payload (contains the claims or user data), and Signature (verifies the token's integrity).

intermediate

How does JWT help with API authorization?

JWT carries user roles and permissions inside its payload, so APIs can check these claims to allow or deny access to resources without extra database lookups.

What is the main advantage of using JWT in APIs?

A It replaces the need for HTTPS

B It encrypts all API data automatically

C It allows stateless authentication without server session storage

D It stores user passwords securely

JWT allows stateless authentication by storing user info in the token, so the server does not need to keep session data.

Which part of the JWT ensures the token has not been altered?

A Signature

B Header

C Payload

D Claims

The Signature part verifies the token's integrity and confirms it has not been tampered with.

Why is JWT considered useful for scaling APIs?

A Because it is stateless and does not require server session storage

B Because it stores session data on the server

C Because it uses XML format

D Because it requires a database lookup for every request

JWT is stateless, so servers do not need to store session data, making it easier to scale APIs.

What kind of information is typically stored inside the JWT payload?

A User credentials like passwords

B API endpoint URLs

C Server configuration data

D User claims like roles and permissions

The payload contains claims such as user roles and permissions used for authorization.

Which technology is commonly used alongside JWT to secure API communication?

A FTP

B HTTPS

C HTTP

D SMTP

HTTPS encrypts the communication channel, protecting JWT tokens from interception.

Explain why JWT is important for securing APIs and how it supports stateless authentication.

Think about how JWT carries user data and how servers check it without saving sessions.

Describe the structure of a JWT and the role each part plays in API security.

Remember the three parts separated by dots.

Practice

1. Why is JWT important for APIs in Spring Boot?

easy

A. It replaces the need for HTTPS in API communication.

B. It stores user passwords in the token for quick access.

C. It securely identifies users without storing session data on the server.

D. It automatically encrypts all API responses.

Solution

1. Step 1: Understand JWT's role in user identification

   JWT carries user identity information inside the token, so the server does not need to keep session data.

2. Step 2: Recognize security benefits

   This stateless approach improves security and scalability by avoiding server-side session storage.

3. Final Answer:

   It securely identifies users without storing session data on the server. -> Option C

4. Quick Check:

   JWT = stateless secure user ID [OK]

Hint: JWT carries user info, no server session needed [OK]

Common Mistakes:

• Thinking JWT stores passwords inside the token
• Believing JWT replaces HTTPS
• Assuming JWT encrypts API responses automatically

2. Which of the following is the correct way to include a JWT in an HTTP request header?

easy

A. Auth-Token: <token>

B. Authorization: Bearer <token>

C. Token: JWT <token>

D. JWT-Authorization: Bearer <token>

Solution

1. Step 1: Recall standard JWT header format

   The standard way to send JWTs is in the Authorization header with the Bearer scheme.

2. Step 2: Match the correct syntax

   "Authorization: Bearer <token>" is the correct and widely accepted format.

3. Final Answer:

   Authorization: Bearer <token> -> Option B

4. Quick Check:

   JWT header = Authorization: Bearer [OK]

Hint: JWT goes in Authorization header with Bearer prefix [OK]

Common Mistakes:

• Using non-standard header names like Token or Auth-Token
• Omitting the Bearer prefix
• Adding extra words like JWT-Authorization

3. Given this Spring Boot controller method snippet, what will happen if the JWT is missing or invalid?

@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);
    // Assume validateToken returns false if token invalid
    if (!jwtService.validateToken(token)) {
        return ResponseEntity.status(401).body("Unauthorized");
    }
    return ResponseEntity.ok("User profile data");
}

medium

A. Returns 500 Internal Server Error on invalid JWT.

B. Returns 200 OK with user profile regardless of JWT.

C. Throws a NullPointerException if JWT is missing.

D. Returns 401 Unauthorized if JWT is missing or invalid.

Solution

1. Step 1: Check handling of missing or malformed Authorization header

   The code returns 401 Unauthorized if the header is missing or does not start with "Bearer ".

2. Step 2: Check token validation logic

   If the token is invalid, the method also returns 401 Unauthorized.

3. Final Answer:

   Returns 401 Unauthorized if JWT is missing or invalid. -> Option D

4. Quick Check:

   Missing/invalid JWT = 401 Unauthorized [OK]

Hint: Missing or bad JWT triggers 401 Unauthorized [OK]

Common Mistakes:

• Assuming it returns 200 OK without JWT
• Expecting exceptions instead of 401 response
• Thinking it returns 500 error on invalid token

4. Identify the bug in this Spring Boot JWT filter snippet:

public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
    HttpServletRequest req = (HttpServletRequest) request;
    String authHeader = req.getHeader("Authorization");
    if (authHeader != null && authHeader.startsWith("Bearer ")) {
        String token = authHeader.substring(7);
        if (jwtService.validateToken(token)) {
            SecurityContextHolder.getContext().setAuthentication(null);
        }
    }
    chain.doFilter(request, response);
}

medium

A. It sets authentication to null instead of a valid Authentication object.

B. It does not check if authHeader is null before substring.

C. It calls chain.doFilter before validating the token.

D. It uses the wrong header name for JWT.

Solution

1. Step 1: Analyze authentication setting logic

   The code sets authentication to null even when the token is valid, which means no user is authenticated.

2. Step 2: Understand correct behavior

   It should set a valid Authentication object to represent the logged-in user, not null.

3. Final Answer:

   It sets authentication to null instead of a valid Authentication object. -> Option A

4. Quick Check:

   Valid token must set Authentication, not null [OK]

Hint: Valid token must set Authentication object, not null [OK]

Common Mistakes:

• Ignoring that authentication is set to null
• Thinking substring without null check causes error here
• Assuming chain.doFilter order is wrong
• Believing header name is incorrect

5. You want your Spring Boot API to allow users to stay logged in without server sessions, using JWT. Which approach best achieves this while keeping the API stateless and secure?

hard

A. Generate a JWT after login containing user info, send it to client, and require it in Authorization header for each request.

B. Store user sessions in a database and send session IDs in cookies to clients.

C. Send user credentials with every API request and validate each time on the server.

D. Use JWT only for login, then switch to server sessions for other requests.

Solution

1. Step 1: Understand stateless authentication with JWT

   JWT tokens carry user info and are sent by clients with each request, so the server does not store session data.

2. Step 2: Compare with other methods

   Storing sessions or sending credentials every time breaks statelessness or security best practices.

3. Final Answer:

   Generate a JWT after login containing user info, send it to client, and require it in Authorization header for each request. -> Option A

4. Quick Check:

   JWT = stateless secure token per request [OK]

Hint: JWT tokens keep API stateless and secure per request [OK]

Common Mistakes:

• Using server sessions instead of JWT for statelessness
• Sending credentials on every request
• Switching between JWT and sessions inconsistently