jwtk/jjwt · error · MissingClaimException

Missing '<expectedClaimName>' claim. Expected value: <expect

Error message

Missing '<expectedClaimName>' claim. Expected value: <expectedClaimValue>

What it means

Thrown as MissingClaimException when a required claim configured via parser.require(claimName, expectedValue) is entirely absent from the parsed JWT's claims set. JJWT only checks this during parse when claim requirements were registered on the builder.

Source

Thrown at impl/src/main/java/io/jsonwebtoken/impl/DefaultJwtParser.java:756

            if (expectedClaimValue instanceof Date) {
                try {
                    actualClaimValue = claims.get(expectedClaimName, Date.class);
                } catch (Exception e) {
                    String msg = "JWT Claim '" + expectedClaimName + "' was expected to be a Date, but its value " +
                            "cannot be converted to a Date using current heuristics.  Value: " + actualClaimValue;
                    throw new IncorrectClaimException(header, claims, expectedClaimName, expectedClaimValue, msg);
                }
            }

            if (actualClaimValue == null) {
                boolean collection = expectedClaimValue instanceof Collection;
                String msg = "Missing '" + expectedClaimName + "' claim. Expected value";
                if (collection) {
                    msg += "s: " + expectedClaimValue;
                } else {
                    msg += ": " + expectedClaimValue;
                }
                throw new MissingClaimException(header, claims, expectedClaimName, expectedClaimValue, msg);
            } else if (expectedClaimValue instanceof Collection) {
                Collection<?> expectedValues = (Collection<?>) expectedClaimValue;
                Collection<?> actualValues = actualClaimValue instanceof Collection ? (Collection<?>) actualClaimValue :
                        Collections.setOf(actualClaimValue);
                for (Object expectedValue : expectedValues) {
                    if (!Collections.contains(actualValues.iterator(), expectedValue)) {
                        String msg = String.format(MISSING_EXPECTED_CLAIM_VALUE_MESSAGE_TEMPLATE,
                                expectedValue, expectedClaimName, actualValues);
                        throw new IncorrectClaimException(header, claims, expectedClaimName, expectedClaimValue, msg);
                    }
                }
            } else if (!expectedClaimValue.equals(actualClaimValue)) {
                String msg = String.format(INCORRECT_EXPECTED_CLAIM_MESSAGE_TEMPLATE,
                        expectedClaimName, expectedClaimValue, actualClaimValue);
                throw new IncorrectClaimException(header, claims, expectedClaimName, expectedClaimValue, msg);
            }
        }
    }

View on GitHub (pinned to fb71496164)

Solutions

1. Fix the token producer to include the required claim.
2. Remove or correct the require(...) call if the claim is genuinely optional.
3. Check the claim name spelling against what the issuer actually emits (decode the payload to verify).
4. Coordinate claim requirements across services; version the token schema if producers and consumers deploy independently.

Example fix

// before
Jwts.parser().require("tenant", "acme").verifyWith(key).build().parse(jwt); // token lacks 'tenant'
// after
// producer:
String jwt = Jwts.builder().claim("tenant", "acme").signWith(key).compact();
// or consumer: drop the requirement if optional
Jwts.parser().verifyWith(key).build().parse(jwt);

io.jsonwebtoken.Claims c = Jwts.parser().build().parseUnsecuredClaims(jwt).getPayload();
if (!c.containsKey("tenant")) {
    throw new IllegalStateException("Token lacks required claim 'tenant'");
}

try {
    claims = Jwts.parser().require("tenant", "acme").verifyWith(key).build().parseSignedClaims(jwt).getPayload();
} catch (io.jsonwebtoken.MissingClaimException e) {
    // reject token; log e.getClaimName()
}

When it happens

Trigger: Calling DefaultJwtParserBuilder.require("aud", value) (or requireExpiration, requireIssuedAt, etc.) and then parsing a JWT that does not contain that claim name at all.

Common situations: Verifier expects an 'aud'/'iss'/'role' claim the token producer never set; tokens issued by an older version of the producing service lacking newly-required claims; copy-pasted require() calls referencing misspelled claim names.

Related errors

• JWT Claim '<expectedClaimName>' was expected to be a Date, b
• Missing expected '<expectedValue>' value in '<expectedClaimN
• Expected <expectedClaimName> claim to be: <expectedClaimValu
• Unexpected unsecured Claims JWT.
• Unexpected content JWS.

AI-assisted analysis of jwtk/jjwt@fb71496164 (2026-09-09). Data as JSON: /api/errors/024521a23320cb1d. Report an issue: GitHub.