Add support for the AWS_MSK_IAM SASL mechanism #313
Merged
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
Dawnflash
force-pushed
the
msk-iam
branch
2 times, most recently
from
26c8407
to
3ab9a9c
Compare
|
@birdayz Is this going to be wrapped into a new |
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.
AWS_MSK_IAM is an
OAUTHBEARER-based SASL mechanism for accessing AWS MSK clusters using AWS IAM.The OAUTH token is supplied by AWS APIs so it fits nicely into the already written OAUTH token provider.
Uses https://github.com/aws/aws-msk-iam-sasl-signer-go with the region inferred by the AWS SDK. I decided not to add explicit region configuration to the config to keep it cleaner but that would be an easy addition as well.
Resolves #198.