oidc-provider is an OpenID Provider implementation of OpenID Connect. It allows to export a complete mountable or standalone OpenID Provider implementation. This implementation does not dictate a fixed data model or persistence store, instead, you must provide adapters for these. A generic in-memory adapter is available to get you started as well as feature-less dev-only views to be able to get off the ground.
v6.0.0-alpha.0 is now available on npm and master branch, please head over to #419 to provide feedback.
I'm looking for early adopter feedback and pointers to missing changelog entries as well as misunderstood changes. Throughout the v6.0.0 prerelease line the changelog will be extended and especially interaction documentation will be provided.
The minimal node version for this alpha is v11.8.0 and v6.0.0 will release as stable sometime after v12.0.0 lands in April 2019.
npm i oidc-provider@alphaSee v5.x for the last v5.x release and docs.
Table of Contents
- Implemented specs & features
- Certification
- Get started
- Configuration and Initialization
- Debugging
- Events
The following specifications are implemented by oidc-provider. Note that not all features are enabled by default, check the configuration section on how to enable them.
- OpenID Connect Core 1.0
- Authorization (Authorization Code Flow, Implicit Flow, Hybrid Flow)
- UserInfo Endpoint and ID Tokens including Signing and Encryption
- Passing a Request Object by Value or Reference including Signing and Encryption
- Public and Pairwise Subject Identifier Types
- Offline Access / Refresh Token Grant
- Client Credentials Grant
- Client Authentication incl. client_secret_jwt and private_key_jwt methods
- OpenID Connect Discovery 1.0
- OpenID Connect Dynamic Client Registration 1.0
- OAuth 2.0 Form Post Response Mode
- RFC7636 - Proof Key for Code Exchange by OAuth Public Clients
- RFC7009 - OAuth 2.0 Token Revocation
- RFC7662 - OAuth 2.0 Token Introspection
- RFC8252 - OAuth 2.0 for Native Apps BCP
The following drafts/experimental specifications are implemented by oidc-provider.
- JWT Response for OAuth Token Introspection - draft 02
- JWT Secured Authorization Response Mode for OAuth 2.0 (JARM) - draft 02
- OAuth 2.0 Device Authorization Grant - draft 15
- OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens - draft 12
- OAuth 2.0 Resource Indicators - draft 02
- OAuth 2.0 Web Message Response Mode - draft 00
- OpenID Connect Back-Channel Logout 1.0 - draft 04
- OpenID Connect Front-Channel Logout 1.0 - draft 02
- OpenID Connect Session Management 1.0 - draft 28
- RFC7592 - OAuth 2.0 Dynamic Client Registration Management Protocol (Update and Delete)
Updates to draft and experimental 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.
Missing a feature? - If it wasn't already discussed before, ask for it.
Found a bug? - report it.
Filip Skokan has certified that oidc-provider
conforms to the OP Basic, OP Implicit, OP Hybrid, OP Config, OP Dynamic and OP Form Post profiles
of the OpenID Connect™ protocol.
You may check the example folder or follow a step by step example to see which of those fits your desired application setup.
The examples bundled in this repo's codebase are available for you to experiment with here. Dynamic Registration is open, you can literally register any client you want there. An example client using this provider is available here (uses openid-client).
Also be sure to check the available configuration docs section.
oidc-provider allows to be extended and configured in various ways to fit a variety of uses. See the available configuration.
const Provider = require('oidc-provider');
const configuration = {
// ... see available options /docs
};
const 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);
let server;
(async () => {
await oidc.initialize({ clients });
// express/nodejs style application callback (req, res, next) for use with express apps, see /examples/express.js
oidc.callback
// koa application for use with koa apps, see /examples/koa.js
oidc.app
// or just expose a server standalone, see /examples/standalone.js
server = oidc.listen(3000, () => {
console.log('oidc-provider listening on port 3000, check http://localhost:3000/.well-known/openid-configuration');
});
})().catch((err) => {
if (server && server.listening) server.close();
console.error(err);
process.exitCode = 1;
});oidc-provider uses the debug module internally to log information about various states
of authentication requests, errors and grants. To see all these set the DEBUG environment variable
to oidc-provider:* when launching your app.
There is no filter on what is included in the debug output, since it may end-user Personally identifiable information or client credentials its use is only advised for debugging, not regular logging. Use emitted events to cherry pick the one's of interest to your flows and form your own logs aware of what should and should not be a part of a logged message.
Your oidc-provider instance is an event emitter, using event handlers you can hook into the various
actions and i.e. emit metrics or that react to specific triggers. In some scenarios you can even
change the defined behavior.
See the list of available emitted event names and their description.