PKCE challenge generator
Generate an OAuth PKCE code_verifier and S256 code_challenge.
Loading the tool…
What it does, how to use it, and questions
What it does
PKCE protects public OAuth clients by binding the token request to a high-entropy code_verifier. The authorize request sends code_challenge derived with S256 (SHA-256 then Base64URL) or plain.
This page generates a verifier and challenges. It does not talk to an identity provider.
How to use it
- Generate a pair.
- Copy verifier into your app’s token step and challenge into the authorize URL.
- Prefer S256.
Things to watch for
- Plain challenge is discouraged. Use S256 unless the IdP cannot support it.
- Never log verifiers in production analytics.
Questions
- Does this log me in?
- No.
- How long is the verifier?
- A URL-safe string of sufficient length from the browser’s secure random source.
- Where do I put the challenge?
- On the authorize request as code_challenge and code_challenge_method=S256.
- Is anything sent?
- No.