Relative path of the IDP entry point.
Used to generate the OIDC provider.
All routes handling the custom IDP behaviour.
Used for rendering responses.
Used for POST requests that need to be handled by the OIDC library.
Converts errors to responses.
Renders error responses.
Checks if the input data can be handled by this class. Throws an error if it can't handle the data.
Input data that could potentially be handled.
A promise resolving if the input can be handled, rejecting with an Error if not.
Finds a route that supports the given request.
Find a route by matching the prompt.
Find a route by matching the URL.
Handles the given input. This should only be done if the canHandle function returned true.
Therefore, consider using the handleSafe function instead.
A promise resolving when the handling is finished. Return value depends on the given type.
Finds the matching route and resolves the request.
Input data that will be handled if it can be handled.
A promise resolving if the input can be handled, rejecting with an Error if not. Return value depends on the given type.
Handles the behaviour of an InteractionRoute. Will error if the route does not support the given request.
GET requests go to the templateHandler, POST requests to the specific InteractionHandler of the route.
Handles all requests relevant for the entire IDP interaction, by sending them to either a matching InteractionRoute, or the generated Provider from the ProviderFactory if there is no match.
The InteractionRoutes handle all requests where we need custom behaviour, such as everything related to generating and validating an account. The Provider handles all the default request such as the initial handshake.
This handler handles all requests since it assumes all those requests are relevant for the IDP interaction. A RouterHandler should be used to filter out other requests.