-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add SASL/SCRAM authentication to Kafka receiver and exporter #5009
Labels
comp:kafka
Kafka related issues
Comments
Hey @altieresfreitas , I believe you're referring to IBM/sarama#1985 ? |
tigrannajaryan
pushed a commit
that referenced
this issue
Oct 26, 2021
This allows for developers to use this the existing kafka exporter and use the newly minted AWS_MSK_IAM SASL auth. **Link to tracking Issue:** #5009 In a very loose definition of related ticket. **Testing:** I have some rather basic testing locally to see what I can get done with this. I had followed https://github.com/aws/aws-msk-iam-auth#details as close as I could with this. **Documentation:** I haven't added any new documentation for this since I hadn't have the chance to actually validate this in a production like setting so I am hoping to leave it as a dark feature for the time being.
Hey @alolita , This work as been done (see https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/kafkaexporter/authentication.go#L43) |
It has been added here, time to close this PR ^^ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I would like to use SASL/SCRAM authentication mechanism on kafka receiver and exporter.
The current authentication mechanisms implemented on collector are not supported by AWS MSK
Describe the solution you'd like
SASL/SCRAM authentication mechanism is already supported by sarama, the library used by collector.
We could implement this on authentication.go using the same library, adding a SCRAMConfig struct and a new function to configure SCRAM.
Describe alternatives you've considered
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: