Bearer token support for Kafka broker to authenticate to use JWKS / Introspection endpoints #217
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r introspection endpoint Signed-off-by: Marko Strukelj <[email protected]>
scholzj
approved these changes
Jan 23, 2024
ppatierno
approved these changes
Jan 23, 2024
|
While Travis CI hasn't managed to run, locally running the full testsuite passes fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the following configuration options for use when configuring the listener:
oauth.server.bearer.tokenoauth.server.bearer.token.locationThe authentication configuration rules for configuring the introspection endpoint have been relaxed. Introspection endpoint can now be unprotected (no authentication configured on the listener) or it can be protected with
oauth.client.idandoauth.client.secretto sendBasicAuthorizationheader or with theoauth.server.bearer.tokenoroauth.server.bearer.token.locationwhen sendingBearerAuthorizationheader.JWKS endpoint can now also be protected in the same way.