Skip to content

From this site’s maintainer: oidfed — Trust infrastructure for OpenID4VCI, OpenID4VP, and OpenID Connect.

Diagram showing OpenID Connect flow between Provider, Client, and User

oidc-provider

OpenID Certified™ OAuth 2.0 and OpenID Connect Authorization Server for Node.js.

Trust infrastructure for OpenID4VCI, OpenID4VP, and OpenID Connect

Establish trust between credential issuers, wallet providers, and verifiers, or between OpenID Providers and Relying Parties. Use oidfed’s JavaScript and TypeScript libraries to discover participants, validate trust chains, and apply metadata policies through OpenID Federation.

Another open-source project by this site’s maintainer.

Getting Started

Set up your OIDC provider from scratch — configuration basics, account integration, and framework mounting.

Quick Start →

Configuration

Deep-dive into adapters, claims, clients, features, interactions, tokens, cookies, JWKS, PKCE, and more.

Configuration →

Guides

Practical guides for user flows, custom grant types, middleware registration, proxy setup, and context access.

Guides →

Events

Complete reference of all events emitted by the provider for logging, monitoring, and custom integrations.

Events →

API Reference

Auto-generated TypeScript API docs for all oidc-provider types, interfaces, and classes.

API Reference →

Community

Join the discussion — ask questions, share guides, and connect with other users.

GitHub Discussions →

Specification Status Reference
RFC6749 - OAuth 2.0 Stable Read
OIDC Core 1.0 Stable Read
OIDC Discovery 1.0 Stable Read
RFC8414 Authorization Server Metadata Stable Read
OIDC Dynamic Client Registration 1.0 Stable Read
RFC7591 - OAuth 2.0 Dynamic Client Registration Protocol Stable Read
RFC7592 - OAuth 2.0 Dynamic Client Registration Management Protocol Stable Read
OIDC RP-Initiated Logout 1.0 Stable Read
OIDC Back-Channel Logout 1.0 Stable Read
RFC7009 - OAuth 2.0 Token Revocation Stable Read
RFC7636 - Proof Key for Code Exchange (PKCE) Stable Read
RFC7662 - OAuth 2.0 Token Introspection Stable Read
RFC8252 - OAuth 2.0 for Native Apps BCP (AppAuth) Stable Read
RFC8628 - OAuth 2.0 Device Authorization Grant (Device Flow) Stable Read
RFC8705 - OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens (MTLS) Stable Read
RFC8707 - OAuth 2.0 Resource Indicators Stable Read
RFC9101 - OAuth 2.0 JWT-Secured Authorization Request (JAR) Stable Read
RFC9126 - OAuth 2.0 Pushed Authorization Requests (PAR) Stable Read
RFC9207 - OAuth 2.0 Authorization Server Issuer Identifier in Authorization Response Stable Read
RFC9396 - OAuth 2.0 Rich Authorization Requests Stable Read
RFC9449 - OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP) Stable Read
RFC9701 - JWT Response for OAuth Token Introspection Stable Read
FAPI 1.0 Security Profile - Part 2: Advanced (FAPI 1.0) Stable Read
FAPI 2.0 Security Profile (FAPI 2.0) Stable Read
FAPI 2.0 Message Signing (FAPI 2.0) Stable Read
JWT Secured Authorization Response Mode for OAuth 2.0 (JARM) Stable Read
OIDC Client Initiated Backchannel Authentication Flow (CIBA) Stable Read
OIDC Relying Party Metadata Choices 1.0 Stable Read
Financial-grade API: Client Initiated Backchannel Authentication Profile (FAPI-CIBA) - Implementers Draft 01 Experimental Read
OAuth 2.0 Attestation-Based Client Authentication - Draft 12 Experimental Read
OAuth Client ID Metadata Document (CIMD) - Draft 03 Experimental Read
OpenID for Verifiable Credential Issuance 1.0 Experimental Read

Supported Access Token Formats:

All credit goes to @panva, author and maintainer of node-oidc-provider. The library, its features, and all upstream documentation are entirely his work. This site is an unofficial community resource that reorganizes that documentation for easier browsing.