feat: add custom oauth bearer authentication support #548
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.
Description
Expose
SetOAuthBearerTokenRefreshHandler
and oauth properties in security information.Fixes #417
How Has This Been Tested?
I've run this locally and confirmed that the OAuth callbacks are called correctly by the Kafka admin client, consumer and producer. Unit tests seem difficult to implement in this case, because the underlying code calls directly into PInvoke code that can't be mocked. Happy to take advice on where unit tests could be added.
Checklist
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement