OIDC Metadata and JWKS Consistency Checker
Compare supplied discovery metadata and public JWKS without contacting an identity provider.
Loading tool…
How to use OIDC Metadata and JWKS Consistency Checker
Compare supplied discovery metadata and public JWKS without contacting an identity provider. Check exact issuer identity, HTTPS endpoint syntax, advertised signing algorithms, duplicate kid values and a bounded subset of public asymmetric JWK structures.
- Provide discovery metadata json, public jwks json, expected exact issuer.
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- 100KB per document,200KB total,100 public keys,40levels. Private/symmetric key material is rejected.
- Mechanical consistency is not discovery conformance, trust, login readiness or signature verification. No network requests occur.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Does matching metadata make an identity provider trustworthy?
No. These are consistency checks on supplied documents. Authentic retrieval and issuer/key trust must be established separately.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All developer →JWT Signature Verifier
Verify a JWT signature against an explicit public JWK and selected claims.
DeveloperJWK and PEM Public Key Converter
Convert RSA or P-256 public keys between JWK JSON and SPKI PEM locally.
DeveloperOAuth PKCE S256 Workbench
Generate a random PKCE verifier/challenge or check a supplied S256 pair locally.
DeveloperSSH Authorized Keys Options Inspector
Inspect authorized_keys options, supported public-key records and SHA256 fingerprints locally.