Class ClientRegistrationFilter
- All Implemented Interfaces:
Filter
All OpenID metadata must be included in the OAuth2ClientFilter
configuration,
in the "metadata" attribute. Note that for dynamic client registration,
only the "redirect_uris" attribute is mandatory. Notably, where private_key_jwt authentication
is configured, the "jwks" metadata should be omitted as this will be determined by the
ClientRegistrationFilter
from the configured discoverySecretId
.
The supplied ClientRegistrationStrategy
determines the authentication mechanism used.
-
Constructor Summary
ConstructorsConstructorDescriptionClientRegistrationFilter
(org.forgerock.openig.filter.oauth2.client.ClientRegistrationRepository repository, ClientRegistrationStrategy registrationStrategy) Creates a new dynamic registration filter. -
Method Summary
-
Constructor Details
-
ClientRegistrationFilter
public ClientRegistrationFilter(org.forgerock.openig.filter.oauth2.client.ClientRegistrationRepository repository, ClientRegistrationStrategy registrationStrategy) Creates a new dynamic registration filter.- Parameters:
repository
- TheClientRegistrationRepository
holding the registrations values.registrationStrategy
- TheClientRegistrationStrategy
used to conduct client registration.
-
-
Method Details
-
filter
public Promise<Response,NeverThrowsException> filter(Context context, Request request, Handler next) Description copied from interface:Filter
Filters the request and/or response of an exchange. To pass the request to the next filter or handler in the chain, the filter callsnext.handle(context, request)
.This method may elect not to pass the request to the next filter or handler, and instead handle the request itself. It can achieve this by merely avoiding a call to
next.handle(context, request)
and creating its own response object. The filter is also at liberty to replace a response with another of its own by intercepting the response returned by the next handler.
-