-
Notifications
You must be signed in to change notification settings - Fork 801
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
Support configuration of other SASL mechanisms #526
Comments
I am a Go noob but I was able to get SCRAM sha256 and sha512 working using this patch
and this dockerfile
if they are of any help to anyone |
@jbresciani your patch works like a charm!!! Good work and thanks!!! |
Hi @tsrikanth06 @jbresciani - Could you provide the config that worked for you please? I tried with this patch but I still get
config:
@bai - Tagging you because I see that most of the recent commits are from you. Could you please help with SASL_SSL configuration for Burrow? |
my config currently looks like
with the following ENV var's set in the burrow pod at deploy time, this way I don't need to hardcode them in the configmap and then store secrets in git.
|
I've since moved to SASL_SSL and my config now looks like
|
Thanks @jbresciani for providing your config. I tried this configuration (using this patch and also the master branch) but it still fails with the same error. I tried creating the pem file from the client.jks using the following command. Is this the right approach?
|
It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526
This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526
This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526
This includes: 1. Add SASL-SCRAM ability to Kafka connection This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526 2. Ignore ZooKeeper znode Create if the path already exists Currently, Burrow will attempt to create the znode used by Burrow on startup This will cause problems if there is authentication needed when connecting to zk. The fix is to ignore creating zk node paths if it already exists 3. Yext specific Dockerfile the config file and dir used by Burrow is updated for M4 and Khan 4. Update module and import references go build -o build/Burrow github.com/yext/Burrow pulls in linkedin's branch of Burrow Changing references of linkedin to current fork
This includes: 1. Add SASL-SCRAM ability to Kafka connection This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526 2. Ignore ZooKeeper znode Create if the path already exists Currently, Burrow will attempt to create the znode used by Burrow on startup This will cause problems if there is authentication needed when connecting to zk. The fix is to ignore creating zk node paths if it already exists 3. Yext specific Dockerfile the config file and dir used by Burrow is updated for M4 and Khan 4. Update module and import references go build -o build/Burrow github.com/yext/Burrow pulls in linkedin's branch of Burrow Changing references of linkedin to current fork
I have also tried @jbresciani and it works |
Added fixes for linkedin#347 linkedin#526
This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526
This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses #526
* Add SASL-SCRAM ability to Kafka connection This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 It adds an entry in the SASL Profile configuration called key=mechanism value type=string required=no default value=(empty) Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512 Partially addresses linkedin#526 * Ignore ZooKeeper znode Create if the path already exists Currently, Burrow will attempt to create the znode used by Burrow on startup This will cause problems if there is authentication needed when connecting to zk. The fix is to ignore creating zk node paths if it already exists * Yext specific Dockerfile the config file and dir used by Burrow is updated for M4 and Khan * Update module and import references go build -o build/Burrow github.com/rjh-yext/Burrow pulls in linkedin's branch of Burrow Changing references of linkedin to current fork * Fix Travis CI build. * Add Prometheus Metrics Exporter * Add support for Kafka 2.5.0 anf Go 1.14 * NameToCertificate only allows associating a single certificate with a given name. Leave that field nil to let the library select the first compatible chain from Certificates. * Update sarama with a fix for IBM/sarama#1692 * Removing CI jobs from upstream merge. Co-authored-by: Roger Hwang <[email protected]> Co-authored-by: rjh-yext <[email protected]> Co-authored-by: klDen <[email protected]> Co-authored-by: Michael Wain <[email protected]> Co-authored-by: Vlad Gorodetsky <[email protected]> Co-authored-by: Vlad Gorodetsky <[email protected]>
So can this patch be added to the project? Looks like burrow only supports PLAINTEXT SASL mechanism, and I need SHA512... |
Ignore. Turns out you can set SASL mechanism: https://github.com/linkedin/Burrow/blob/master/core/internal/helpers/sarama.go#L129-L139 Example config:
I am still blaming documentation because this was not mentioned... 😠 |
Currently, there is no way to configure the SASL mechanism in a SASL Profile. So it defaults to PLAIN
Looks like we simply need to set the mechanism here based on configuration: https://github.com/linkedin/Burrow/blob/master/core/internal/helpers/sarama.go#L114
Then we will be able to support the following SASL Mechanisms https://github.com/Shopify/sarama/blob/master/broker.go#L55
The text was updated successfully, but these errors were encountered: