Report

Help us improve this tool

OIDC Discovery Inspector

Parse OpenID Connect discovery JSON, list endpoints, signing algorithms, and supported grant types in your browser.

O M T

What is an OpenID Connect discovery document?

An OpenID Provider publishes machine-readable metadata at /.well-known/openid-configuration. The JSON lists the issuer, OAuth/OIDC endpoints (authorize, token, JWKS), supported response types, grant types, signing algorithms, and optional extension fields. Client libraries and security reviews use this file to configure redirect URIs, scopes, and token validation without hard-coding provider URLs.

How to use this inspector

  1. Fetch discovery JSON from your identity provider or paste a saved copy.
  2. Review grouped endpoint URLs and capability arrays (scopes, algorithms, grants).
  3. Read warnings for missing common endpoints or non-HTTPS issuers.

Pair this with OAuth Authorization URL Builder, OAuth PKCE Generator, and JWKS Inspector when wiring a new OIDC client.

Frequently Asked Questions

Is the discovery JSON uploaded?

No. Parsing runs entirely in your browser. Paste only non-production metadata if you are unsure.

Does this validate TLS or fetch live URLs?

No. You paste static JSON. Live discovery fetch and certificate pinning are out of scope.

Which fields are required?

OpenID Connect Discovery requires issuer. Production providers also publish authorization, token, and JWKS endpoints; the tool warns when those keys are absent.