Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to implement a custom SASL mechanism and deprecate the previous mechanism #2482

Closed
wants to merge 2 commits into from

Conversation

bpaquet
Copy link

@bpaquet bpaquet commented Jun 29, 2023

@dnwe This is a follow up of #2466

In this PR, I'm replacing the previous mechanisms SCRAM-SHA-256 and SCRAM-SHA-512 by a generic function SCRAMClientExternal 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 and SCRAM-SHA-512 can be implemented with the new API (see examples/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

@Neustradamus
Copy link

Linked to:

@bpaquet
Copy link
Author

bpaquet commented Sep 1, 2023

@dnwe Can I help to move forward with this PR? Thx

@tooptoop4

This comment was marked as spam.

@dtjm
Copy link

dtjm commented Oct 24, 2023

@bpaquet I've added a couple of commits to fix the lint breakage as well as merge in the latest from the main branch if you would like to pull them into your branch: bpaquet#1

@bpaquet
Copy link
Author

bpaquet commented Dec 4, 2023

This PR seems to be useless now, because of https://github.com/aws/aws-msk-iam-sasl-signer-go :)

@bpaquet bpaquet closed this Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants