Allow to implement a custom SASL mechanism and deprecate the previous mechanism #2482
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.
@dnwe This is a follow up of #2466
In this PR, I'm replacing the previous mechanisms
SCRAM-SHA-256
andSCRAM-SHA-512
by a generic functionSCRAMClientExternal
which be used to implement custom auth mechanism, like AWS IAM MSK.This is a breaking change in the config API, as we discussed in the previous PR.
SCRAM-SHA-256
andSCRAM-SHA-512
can be implemented with the new API (seeexamples/sasl_scram_client/main.go
).Implementation of the custom mechanism for AWS IAM MSK: https://github.com/bpaquet/awsIamMskForSarama
Using it in kaf: https://github.com/bpaquet/kaf/tree/msk_iam_3