JSON config for the OIDC library
Remaining parameters required for the factory.
Private Readonly adapterPrivate Readonly basePrivate Readonly configPrivate Readonly credentialPrivate Readonly errorPrivate Readonly interactionPrivate Readonly jwkProtected Readonly loggerPrivate Readonly oidcPrivate Optional providerPrivate Readonly responsePrivate Readonly showPrivate Readonly storagePrivate captureIn the configureErrors function below, we configure the renderError function of the provider configuration.
This function is called by the OIDC provider library to render errors,
but only does this if the accept header is HTML.
Otherwise, it just returns the error object itself as a JSON object.
See https://github.com/panva/node-oidc-provider/blob/0fcc112e0a95b3b2dae4eba6da812253277567c9/lib/shared/error_handler.js#L48-L52.
In this function we override the ctx.accepts function
to make the above code think HTML is always requested there.
This way we have full control over error representation as configured in configureErrors.
We still check the accept headers ourselves so there still is content negotiation on the output,
the client will not simply always receive HTML.
Should this part of the OIDC library code ever change, our function will break, at which point behaviour will simply revert to what it was before.
Private configurePrivate configurePrivate configurePrivate createPrivate createPrivate generatePrivate initCreates a configuration by copying the internal configuration and adding the adapter, default audience and jwks/cookie keys.
Private is
Creates an OIDC Provider based on the provided configuration and parameters. The provider will be cached and returned on subsequent calls. Cookie and JWT keys will be stored in an internal storage so they can be re-used over multiple threads. Necessary claims for Solid OIDC interactions will be added. Routes will be updated based on the
baseUrlandoidcPath.