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 models 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.
Table of Contents
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.
The following drafts/experimental specifications are implemented by oidc-provider.
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.
You may follow an example step by step setup (recommended), or run and experiment with an example server that's part of the repo (if you can follow the structure, if not check the step by step).
The example bundled in this repo's codebase is 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).
oidc-provider allows to be extended and configured in various ways to fit a variety of uses. See the available configuration.
const Provider = ;const configuration =// ... see available options /docs/configuration.md;const clients =client_id: 'foo'client_secret: 'bar'redirect_uris: ''// + other client properties;const oidc = '' configuration;oidc;
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 it's 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.