OpenID Connect ID token checker
Libraries often skip or hide the checks that tie an ID token to the login that produced it. Paste the token and, optionally, what you sent and received: the page recomputes at_hash and c_hash, compares the nonce, issuer and audience, and tells you which check fails and why. Runs in your browser; we only count anonymous visits. It does not verify the signature.
Use test tokens. A real ID token identifies a person. Prefer a token from a test account or a sandbox.
How to use this tool
- Paste the ID token from the token response (not the access token).
- Add your issuer, client_id and the nonce you sent in the authorization request.
- To check the bindings, paste the access token and/or authorization code from the same login.
at_hashis the left half of the hash of the access token;c_hashof the code. The hash is chosen by the token'salg(RS256 uses SHA-256, ES384 uses SHA-384, and so on).
Example
The example button fills the access token and at_hash from the OpenID Connect Core specification's sample, so the binding check matches. Change one character of the access token to see the mismatch message.
Limits
The signature is not verified: use your OIDC library and the provider's published keys for that. Whether at_hash is required depends on the flow (it is required when an access token is returned together with the ID token from the authorization endpoint). The page reports what is present and does not know which flow you used.
Privacy and security of what you enter
Everything is computed in your browser; nothing is uploaded. See the privacy notice.
We configure and review OIDC and OAuth2 setups. See the OAuth2 error doctor, the JWT inspector or the services.
Message us on LinkedIn