Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow restricting OidcRequestFilter to specific OIDC endpoints and scopes #37256

Closed
sberyozkin opened this issue Nov 21, 2023 · 1 comment · Fixed by #37257
Closed

Allow restricting OidcRequestFilter to specific OIDC endpoints and scopes #37256

sberyozkin opened this issue Nov 21, 2023 · 1 comment · Fixed by #37257
Labels
area/oidc kind/enhancement New feature or request
Milestone

Comments

@sberyozkin
Copy link
Member

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 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

@sberyozkin sberyozkin added the kind/enhancement New feature or request label Nov 21, 2023
Copy link

quarkus-bot bot commented Nov 21, 2023

/cc @pedroigor (oidc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/oidc kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant