FREE TOOLS
OIDC Token Claim Checker
Compare decoded token claims with supplied issuer, audience, nonce and time expectations.
JWT compact token, Expected issuer, Expected audience, Expected nonce, Comparison Unix seconds, Allowed clock skew seconds
oidc-token-claim-checker.json (complete report)
Browser only
Runs locally in your browser. Your files, pasted content and generated output are not uploaded. Reset clears this tool’s working data.
This tool needs JavaScript. If it does not load, refresh the page and try again.
How to use this tool
- Enter values using the examples, or choose a local file where requested. Follow the displayed supported input shapes and limits.
- Choose Calculate result and inspect the complete result.
- Download result to save the primary file. Where supplied, additional links save source files and the full JSON report. Reset restores examples and clears output.
Examples
JWT compact token: eyJhbGciOiJub25lIn0.eyJpc3MiOiJodHRwczovL2lzc3Vlci5leGFtcGxlLmNvbSIsImF1ZCI6ImRlbW8iLCJzdWIiOiJhZGEiLCJleHAiOjIwMDAsImlhdCI6NTAwLCJuYmYiOjYwMCwibm9uY2UiOiJhYmMifQ.
Expected issuer: https://issuer.example.com
Expected audience: demo
Expected nonce: abc
Comparison Unix seconds: 1000
Allowed clock skew seconds: 0
Limitations
- Compare required string issuer/nonce,string-or-array audience,numeric exp/iat and optional nbf against supplied exact expectations and explicit Unix time/skew. Canonical three-part JWT only; reject critical/unencoded extensions. Malformed input refuses; valid mismatches report failed checks. No signature,key trust,azp,transport or identity verification; this is not complete OIDC token validation.
- Text fields are limited to100,000 UTF16 units each and400,000 combined UTF8 bytes; file fields have their own displayed limits. Combined output is at most4MiB. Processing stops after30 seconds; tool-specific bounds may be tighter.
- Generated source is a downloadable result and is not executed here. Inspection does not establish remote behavior, trust or standards certification.