You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now a custom OIDC Request filter will be invoked for all of OIDC endpoint requests. For example, if these requests are done by quarkus-oidc then it can be up to 5 endpoints, so the filter which may want to intercept a JWKS endpoint request will need to filter request paths etc.
Additionally, if quarkus-oidc-client is used alongside quarkus-oidc then the filter will also be run when quarkus-oidc-client makes requests to the token endpoint
Implementation ideas
Allow each filter restrict its application to a specific OIDC endpoint and scope with 2 enums
The text was updated successfully, but these errors were encountered:
Description
Right now a custom OIDC Request filter will be invoked for all of OIDC endpoint requests. For example, if these requests are done by
quarkus-oidc
then it can be up to 5 endpoints, so the filter which may want to intercept a JWKS endpoint request will need to filter request paths etc.Additionally, if
quarkus-oidc-client
is used alongsidequarkus-oidc
then the filter will also be run whenquarkus-oidc-client
makes requests to the token endpointImplementation ideas
Allow each filter restrict its application to a specific OIDC endpoint and scope with 2 enums
The text was updated successfully, but these errors were encountered: