Added support for a generic oauthbearer as the sasl mechanism #379
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
This was referenced Feb 6, 2024
|
Hi @Mongey! |
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.
Kafka supports using oauth2 as its authentication mechanism, by setting the sasl mechanism to the type "oauthbearer".
To enable a Kafka client to use this mechanism it needs an implementation of a tokenProvider to acquire tokens.
This pull request contains the code for this tokenProvider, the nessecary configuration options (Only an url that supplies oauth2 tokens), and finally the option to choose oauthbearer as the mechanism for this client.
This would close issue #377
The code has been tested thoroughly as requested.