Advanced JWT diagnostics

OIDC Discovery Checker

Check OpenID Connect or OAuth authorization-server metadata from an issuer URL, validate exact issuer matching and inspect JWKS and endpoint metadata in your browser.

The request runs from your browser with credentials omitted. Some providers do not allow CORS even when their metadata is valid.

How discovery validation fits into JWT verification

OIDC Discovery publishes issuer, authorization_endpoint, jwks_uri and supported capabilities. The returned issuer must exactly match the issuer used for discovery.

OAuth RFC 8414 uses a different well-known path rule when an issuer contains a path component. The checker builds the URL according to the selected mode.

Only the discovery URL you request is fetched. Credentials are omitted and the response is not sent to a JWTDecoder.tools API.