How to use OAuth Flow Helper and PKCE Explainer
- Choose Generate verifier and S256 challenge for fresh test values. This creates a random verifier, its challenge and a separate random state; it does not use the example verifier field.
- Choose Derive S256 from a verifier to check an existing supported verifier. Paste it exactly, without spaces or a trailing newline.
- Choose Inspect an authorization URL to read its supported parameters and observations locally. Use a test URL; the destination is not opened.
- Read the mode’s result. A calculated challenge or well-shaped URL does not establish a registered redirect, session binding, trusted provider or successful authorization.
Example: OAuth Flow Helper and PKCE Explainer
Derive an S256 challenge from the public test verifier.
Options
- PKCE task
- Choose Generate verifier and S256 challenge, Derive S256 from a verifier, Inspect an authorization URL.
- Code verifier
- 43 to 128 ASCII characters from A–Z, a–z, 0–9, hyphen, period, underscore and tilde. Treat a real verifier as a temporary secret.
- Authorization URL to inspect
- Up to 8,192 characters. This tool only inspects parameters; it makes no authorization or token request.
Supported inputs and limits
- Generation and derivation use a 43–128-character supported ASCII verifier and unpadded base64url SHA-256 challenge.
- URL inspection is limited to 8,192 characters and the listed authorization-code/PKCE parameters.
- Generated verifier and state values are independent and are not stored.
- No authorization, token or account request is sent, and no client session, redirect registration or provider behavior is implemented.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A verifier belongs to one authorization attempt
Generate creates a fresh random verifier, its S256 challenge and a separate random state value. Derive calculates the challenge for a supplied verifier. These values belong to one authorization attempt; a public example has no secrecy. The page does not store a flow, bind state to a session, exchange tokens or implement provider safeguards.
Inspecting parameters does not authenticate a provider
URL inspection reads supplied parameters locally and does not open the destination or exchange a code. An expected challenge shape cannot establish that a redirect URI is correctly registered or that state was securely tracked. Verify the full application flow with its provider rather than inferring success from one calculated value.
Questions about OAuth Flow Helper and PKCE Explainer
Does this sign me in?
No. It explains and checks local test inputs without sending an authorization request.
What is hashed for S256?
The exact supported ASCII verifier bytes are SHA-256 hashed, then encoded as unpadded base64url.
Can this replace my application’s state and session checks?
No. A real client still needs the complete protocol, redirect, state, session and token safeguards.