oidc-provider

This module provides an OAuth 2.0 (RFC 6749) Authorization Server with support for OpenID Connect (OIDC) and many other additional features and standards.

Table of Contents

• Implemented specs & features
• Certification
• Documentation & Configuration
• Recipes
• Events

The following specifications are implemented by oidc-provider (not exhaustive):

Note that not all features are enabled by default, check the configuration section on how to enable them.

• RFC6749 - OAuth 2.0 & OIDC Core 1.0
• OIDC Discovery 1.0
• Dynamic Client Registration
  • OIDC Dynamic Client Registration 1.0
  • RFC7591 - OAuth 2.0 Dynamic Client Registration Protocol
  • RFC7592 - OAuth 2.0 Dynamic Client Registration Management Protocol
• OIDC RP-Initiated Logout 1.0
• OIDC Back-Channel Logout 1.0
• RFC7009 - OAuth 2.0 Token Revocation
• RFC7636 - Proof Key for Code Exchange (PKCE)
• RFC7662 - OAuth 2.0 Token Introspection
• RFC8252 - OAuth 2.0 for Native Apps BCP (AppAuth)
• RFC8628 - OAuth 2.0 Device Authorization Grant (Device Flow)
• RFC8705 - OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens (MTLS)
• RFC8707 - OAuth 2.0 Resource Indicators
• RFC9101 - OAuth 2.0 JWT-Secured Authorization Request (JAR)
• RFC9126 - OAuth 2.0 Pushed Authorization Requests (PAR)
• RFC9207 - OAuth 2.0 Authorization Server Issuer Identifier in Authorization Response
• RFC9449 - OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP)
• Financial-grade API Security Profile 1.0 - Part 2: Advanced (FAPI 1.0)
• JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)
• OIDC Client Initiated Backchannel Authentication Flow (CIBA)

Supported Access Token formats:

• Opaque
• JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens

The following draft specifications are implemented by oidc-provider:

• JWT Response for OAuth Token Introspection - draft 10
• Financial-grade API: Client Initiated Backchannel Authentication Profile (FAPI-CIBA) - Implementer's Draft 01
• FAPI 2.0 Security Profile (FAPI 2.0) - Implementer's Draft 02
• FAPI 2.0 Message Signing (FAPI 2.0) - Implementer's Draft 01

Updates to draft specification versions are released as MINOR library versions, if you utilize these specification implementations consider using the tilde ~ operator in your package.json since breaking changes may be introduced as part of these version updates. Alternatively acknowledge the version and be notified of breaking changes as part of your CI.

Filip Skokan has certified that oidc-provider conforms to the following profiles of the OpenID Connect™ protocol.

• Basic, Implicit, Hybrid, Config, Dynamic, Form Post, and 3rd Party-Init
• Back-Channel Logout and RP-Initiated Logout
• FAPI 1.0
• FAPI CIBA
• FAPI 2.0

If you want to quickly add OpenID Connect authentication to Node.js apps, feel free to check out Auth0's Node.js SDK and free plan. Create an Auth0 account; it's free!

If you or your company use this module, or you need help using/upgrading the module, please consider becoming a sponsor so I can continue maintaining it and adding new features carefree. The only way to guarantee you get feedback from the author & sole maintainer of this module is to support the package through GitHub Sponsors.

oidc-provider can be mounted to existing connect, express, fastify, hapi, or koa applications, see how. The provider allows to be extended and configured in various ways to fit a variety of uses. See the documentation and example folder.

import Provider from 'oidc-provider'
const configuration = {
  // refer to the documentation for other available configuration
  clients: [
    {
      client_id: 'foo',
      client_secret: 'bar',
      redirect_uris: ['http://lvh.me:8080/cb'],
      // ... other client properties
    },
  ],
}

const oidc = new Provider('http://localhost:3000', configuration)

oidc.listen(3000, () => {
  console.log(
    'oidc-provider listening on port 3000, check http://localhost:3000/.well-known/openid-configuration',
  )
})

Collection of useful configuration use cases are available over at recipes.

oidc-provider instances are event emitters, using event handlers you can hook into the various actions and i.e. emit metrics that react to specific triggers. See the list of available emitted event names and their description.