iamops.dev
Argo on X RSS feed
ENEnglish

Tools

PKCE code challenge generator

Make a code verifier and its S256 challenge, or check a pair you already have.

Runs in your browser. Nothing you paste leaves your device.

Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.

The page makes no network request while you work. The only exceptions are the buttons that say Fetch, which call the address you type. Keep real private keys out of any web page, including this one.

How to get the input
  1. DevTools > Network with Preserve log on: the authorization request URL holds code_challenge and code_challenge_method.Chrome DevTools: Network
  2. The code_verifier is in the body of the later POST to the token endpoint when the client runs in the browser. For a server-side client, log it in a test setup only.

Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.

What can I paste here#

Nothing is required to generate a pair. To check a pair you already have, paste the code verifier and the S256 challenge.

PKCE generator

Samples are made with throwaway keys and example.test names. They mean nothing outside this page.

How to read the result#

What it does not do#

Questions people ask#

What can I paste here

Nothing is required to generate a pair. To check a pair you already have, paste the code verifier and the S256 challenge.

How do I generate a PKCE code challenge?

Create a random verifier of 43 to 128 characters, take its SHA-256 hash and encode it as base64url. That value is the S256 challenge. This page does it with the Web Crypto random source.

Should I use S256 or plain?

Use S256. Plain sends the verifier in the clear and is only for clients that cannot hash, which is almost never the case today.

Related articles#

The newest posts and labs on the same topic, picked automatically.