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.

Sign up for GitHub

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

Jump to bottom

Flow specific OIDC request/response filter support #46697

Open
sberyozkin opened this issue Mar 10, 2025 · 2 comments
Open

Flow specific OIDC request/response filter support #46697

sberyozkin opened this issue Mar 10, 2025 · 2 comments
Labels
area/oidc kind/enhancement New feature or request

Comments

@sberyozkin
Copy link
Member

sberyozkin commented Mar 10, 2025 •
edited
Loading

Description

OIDC request and response filters can be used to customize how Quarkus OIDC communicates with providers.

If the endpoint supports both bearer and code flows, it can be useful to restrict filters to specific flows only given that the flow can impact how filters are implemented

Implementation ideas

No response
@sberyozkin sberyozkin added the kind/enhancement New feature or request label Mar 10, 2025
@quarkus-bot quarkus-bot
Copy link

quarkus-bot bot commented Mar 10, 2025

/cc @pedroigor (oidc)

@sberyozkin
Copy link
Member Author

sberyozkin commented Mar 10, 2025 •
edited
Loading

Doing a similar flow specific restrictions for custom tenant resolvers is trickier because an access to the tenant configuration can be required in order to check if the token is provided as a bearer token. Perhaps it can be restrict to the Authorization: Bearer token case. CC @calvernaz

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

No branches or pull requests
1 participant
@sberyozkin