Skip to content
All projects
Application Security / SSO & OIDCCompletedShipped Jul 2026

OIDC Discovery Validator

Paste an OpenID Connect discovery document (or an issuer URL) and validate it against the spec — endpoints, flows, PKCE, scopes, and signing algorithms — with PASS/WARN/FAIL findings. The OIDC counterpart to SAMLCheck.

Proposed stack

  • Next.js
  • TypeScript
  • Tailwind CSS
  • jose

Goal

Give identity teams a fast way to sanity-check an OIDC provider's configuration before wiring it up.

Overview

Paste the JSON from a provider's `/.well-known/openid-configuration` (or enter an issuer URL to fetch it) and the tool validates it against the OpenID Connect spec.

It checks required endpoints, HTTPS + issuer-origin consistency, PKCE support (S256), supported scopes and response types, and flags weak or deprecated signing algorithms.

Results come back as a PASS / WARN / FAIL verdict with categorized findings and a parsed summary of the provider's capabilities.

Architecture

Discovery Doc / Issuer URL → OIDC Validator → Spec Checks → Verdict & Findings

Validates an OIDC provider's configuration against the spec so misconfigurations surface before integration.

Key features

  • Paste a discovery doc or fetch it from an issuer URL.
  • Validate required endpoints and HTTPS/issuer consistency.
  • Check PKCE (S256), scopes, and response types.
  • Flag weak/deprecated signing algorithms.
  • PASS / WARN / FAIL verdict with categorized findings.
  • Optionally inspect the provider's JWKS keys.

Technical challenges

  • Covering the OIDC discovery spec's required vs recommended fields accurately.
  • Handling CORS when fetching a live discovery document (paste as the offline fallback).
  • Turning spec checks into clear, actionable PASS/WARN/FAIL findings.

How it's built

  • 1Next.js + TypeScript + Tailwind; validation logic covered by unit tests.
  • 2Fetch via a route handler with a paste fallback; jose for JWKS handling.
  • 3Verified against Google's real discovery document and JWKS.

Interested in this work?

Happy to talk through the design, trade-offs, and implementation plan.

Get in touch