-
Notifications
You must be signed in to change notification settings - Fork 33
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 support for SASL/SCRAM #3
Comments
Hi I'd like to support SASL_SSL. The extension is based on https://github.com/SOHU-Co/kafka-node, which currently only supports the PLAIN mechanism. I am a contributor and could look into SCRAM when possible, but for now PLAIN is the more likely one to be supported. |
Would love SASL_SCRAM... |
But thank you very much |
@winter98 0.7.0 was just pushed which adds SASL/PLAIN. I'll keep this open and track of it and put in SCRAM when it becomes available in dependencies. |
Thanks, appreciate it. |
SASL/SCRAM should be doable (as well as OAUTHBEARER) once the extension uses kafkajs (see #10) : https://kafka.js.org/docs/configuration#a-name-sasl-a-sasl |
@angelozerr if you want to test SASL/SCRAM auth, you can create a free account on https://www.cloudkarafka.com/plans.html |
I did a really quick'n dirty test to implement SASL/SCRAM and it worked (tested against a https://www.cloudkarafka.com/ cluster) : Unfortunately, I can't seem to be able to produce records on that cloudkarafka topic (Error: Not authorized to access topics: [Topic authorization failed]). I don't know whether it's something I missed in my changes or if it's some sort of cluster limitation) |
Anyone interested in seeing SCRAM support, can test PR #67. Please download the vscode-kafka 0.11.0 build for that PR and follow these instructions to install the vsix file in vscode. Feedback is most welcome! |
Hi,
Do you intend to implement SASL_SSL (particularly SASL_SCRAM) connectivity ?
Thanks.
The text was updated successfully, but these errors were encountered: