OpenID Connect ID Token (JWT) Regex for Java

What this pattern does

This page provides a well-structured, multi-part regular expression for matching openid connect id token (jwt), ported and verified for Java. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

// OpenID Connect ID Token (JWT)
// ReDoS-safe | RegexVault — Security > OAuth & OIDC

import java.util.regex.Pattern;

public class OpenidConnectIdTokenJwtValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^([A-Za-z0-9_-]+)\\.([A-Za-z0-9_-]+)\\.([A-Za-z0-9_-]*)$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJ1c2VyMTIzIiwiYXVkIjoiY2xpZW50XzEifQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c")); // true
    }
}

Test Cases

When to use this pattern

This pattern is drawn from the Security > OAuth & OIDC category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Technical Notes

OIDC ID tokens are JWTs with specific required claims: iss (issuer), sub (subject), aud (audience), exp (expiry), iat (issued at). Always validate: 1) signature, 2) iss matches expected provider, 3) aud matches client_id, 4) exp is in the future, 5) nonce (if used). Never trust an ID token without validation.