REGEXVAULTv2.0
Security/OAuth & OIDC
Verified Safe

OAuth 2.0 Authorization Code Regex for Java

/^[A-Za-z0-9\-/_]{20,64}$/

What this pattern does

This page provides a lightweight, single-purpose regular expression for matching oauth 2.0 authorization code, 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

Java
// OAuth 2.0 Authorization Code
// ReDoS-safe | RegexVault — Security > OAuth & OIDC

import java.util.regex.Pattern;

public class Oauth20AuthorizationCodeValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^[A-Za-z0-9\\-/_]{20,64}$");

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

    // Example
    public static void main(String[] args) {
        System.out.println(validate("4/0AY0e-g7aBcDeFgHiJkLmNoPqRsTuVwXyZ01")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
4/0AY0e-g7aBcDeFgHiJkLmNoPqRsTuVwXyZ01short
aBcDeFgHiJkLmNoPqRsTuVwXyZ0123456789code with spaces
code!@#$%^

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

Authorization codes in redirect URIs may be logged by load balancers, CDNs, or proxy servers that log full URLs. Ensure auth callback URLs are excluded from access logging.

Technical Notes

Authorization codes are single-use and short-lived (typically 5-10 minutes). RFC 6749 does not specify the format — implementation-specific. Codes appear in the redirect URI as ?code=VALUE and must be exchanged immediately for an access token.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern