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

Support OIDC Client JWT Bearer authentication #38609

Closed
sberyozkin opened this issue Feb 6, 2024 · 1 comment · Fixed by #38541
Closed

Support OIDC Client JWT Bearer authentication #38609

sberyozkin opened this issue Feb 6, 2024 · 1 comment · Fixed by #38541

Comments

@sberyozkin
Copy link
Member

sberyozkin commented Feb 6, 2024

Description

https://www.rfc-editor.org/rfc/rfc7523 defines how an incoming or possibly stored JWT bearer token can be exchanged using the JWT bearer token grant (already supported by the OIDC client) or be used to authenticate the client as part of whatever grant requests that are made.

For example, the use case in #38458 is to use the token capturing the current client credentials which is periodically recycled in the cluster thus making it a more secure option to authenticate to the OIDC server.

Implementation ideas

This token is obtained out of band as far as the OIDC client is concerned whose job is to acquire tokens, therefore to support the JWT bearer client authentication at the OIDC client filter level a custom filter is required.

This issue is about making creating such custom filters very easy by only having to extend an abstract class and provide a required assertion property.

Going forward it will also benefit other cases where the OIDC client request parameters have to be provided dynamically at the filter level

@quarkus-bot
Copy link

quarkus-bot bot commented Feb 6, 2024

/cc @pedroigor (bearer-token,oidc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant