Spring Security 6 & JWT Authentication · Lesson

JWT Token Revocation Strategies

Explore methods for revoking compromised or logged-out JWTs, such as blacklisting and short-lived tokens.

JWT Token Revocation Strategies is a free Spring Security 6 & JWT Authentication lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Spring Security 6 & JWT Authentication learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Why Revoke JWTs?

JSON Web Tokens (JWTs) are designed to be stateless, meaning the server doesn't need to store session information. While this offers great scalability, it presents a challenge: how do you invalidate a token before its natural expiration?

We need revocation for scenarios like:

User logout
Token compromise (e.g., stolen token)
User role change or account disablement

The Statelessness Challenge

A core principle of JWTs is that once issued and signed, they can be validated without needing to query a database or external service. This means a server doesn't inherently 'know' if a token has been logically invalidated.

To revoke a JWT, you must introduce a mechanism that re-introduces a form of state, allowing the server to check if a token is still considered valid.

Strategy 1: Short-Lived Tokens

The simplest and most fundamental defense against compromised JWTs is to make them short-lived. If an access token expires quickly (e.g., 5-15 minutes), the window of opportunity for an attacker using a stolen token is minimized.

This strategy often pairs with Refresh Tokens (covered in another lesson) to provide a smooth user experience without requiring frequent re-logins.

Strategy 2: Blacklisting Tokens

To achieve immediate revocation, a common strategy is blacklisting. A blacklist is a storage (like a database table or a high-speed cache like Redis) that holds the unique identifiers (JTI claims) of tokens that have been explicitly invalidated.

When a server receives a JWT, it first checks if the token's JTI is present in the blacklist. If it is, the token is rejected, even if it hasn't expired.

Implementing a Blacklist

For an effective blacklist:

Unique ID: Ensure each JWT has a unique JTI (JWT ID) claim.
Storage: Use a fast, persistent store (e.g., Redis, database table) to hold blacklisted JTIs.
Check: Every time a JWT is presented, validate its signature, then check if its JTI is in the blacklist.
Expiration: Blacklisted tokens should still have their expiry respected. The blacklist entry itself can also have a TTL (Time To Live) matching the token's original expiry, to prevent the list from growing indefinitely.

Simulating a Blacklist

Let's look at a simple Java example to understand the blacklisting concept. We'll simulate a token's unique ID and an in-memory blacklist. In a real application, the blacklist would be a persistent, distributed store like Redis.

Blacklist in Action

This code demonstrates how a token ID can be added to a conceptual blacklist and then checked for revocation. Run it to see the output.

import java.util.HashSet;
import java.util.Set;
import java.util.UUID;

public class Main {
    private static Set<String> revokedTokens = new HashSet<>();

    public static void main(String[] args) {
        String userTokenId = UUID.randomUUID().toString();
        System.out.println("User token ID: " + userTokenId);

        // Simulate token validation
        if (!isTokenRevoked(userTokenId)) {
            System.out.println("Token is valid (not revoked).");
        } else {
            System.out.println("Token is revoked!");
        }

        // User logs out or token is compromised
        revokeToken(userTokenId);
        System.out.println("\n--- Token has been revoked ---");

        // Try to validate again
        if (!isTokenRevoked(userTokenId)) {
            System.out.println("Token is valid (not revoked).");
        } else {
            System.out.println("Token is revoked!");
        }
    }

    public static void revokeToken(String tokenId) {
        revokedTokens.add(tokenId);
    }

    public static boolean isTokenRevoked(String tokenId) {
        return revokedTokens.contains(tokenId);
    }
}

Strategy 3: Whitelisting

An alternative, though less common for raw JWTs, is whitelisting. Instead of listing invalid tokens, you maintain a list of all currently valid tokens or session IDs.

When a request comes in, you check if the token/session ID is on this 'allow list'. If it's not present, it's considered invalid. This approach is more typical for traditional session management but can be adapted.

Every active session gets a unique ID.
Store these valid IDs in a database or cache.
Upon logout, remove the ID from the whitelist.

Comparing Strategies

Each strategy has its place:

Short-Lived Tokens: Essential for minimizing risk. Always combine with other strategies.
Blacklisting: Best for specific, immediate invalidation (e.g., logout, compromise). Introduces a state check per request.
Whitelisting: Useful when you need to manage a finite set of active sessions and invalidate many at once (e.g., user disabled, revoke all sessions). Requires state for *all* tokens, which can be a performance consideration for very high-traffic APIs.

Revocation Strategies Check

Which of the following are valid strategies or important considerations for revoking JSON Web Tokens (JWTs) before their natural expiration?

Lesson Summary

In this lesson, we explored how to tackle the challenge of revoking stateless JWTs. We learned that while JWTs are stateless by design, scenarios like user logout or token compromise necessitate invalidation.

Key strategies include:

Using short-lived tokens to minimize risk.
Implementing a blacklist to mark specific tokens as invalid using their JTI.
Considering whitelisting for managing active sessions, though less common for raw JWTs.

The most robust solutions often combine short expiry times with a blacklisting mechanism for immediate revocation needs.

Frequently asked questions

Is the “JWT Token Revocation Strategies” lesson free?

Yes — the full text of “JWT Token Revocation Strategies” is free to read here on the web, and the Spring Security 6 & JWT Authentication course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Spring Security 6 & JWT Authentication course, upgrade to CoddyKit PRO.

What will I learn in “JWT Token Revocation Strategies”?

Explore methods for revoking compromised or logged-out JWTs, such as blacklisting and short-lived tokens. You practise Spring Security 6 & JWT Authentication with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Spring Security 6 & JWT Authentication?

No prior experience is required. Spring Security 6 & JWT Authentication on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “JWT Token Revocation Strategies” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Spring Security 6 & JWT Authentication lesson?

Yes. Every Spring Security 6 & JWT Authentication lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

Implementing Refresh Tokens
JWT Token Revocation Strategies
Secure Token Storage Practices
Rotating Signing Keys and Key Management

← Back to Spring Security 6 & JWT Authentication