-
Notifications
You must be signed in to change notification settings - Fork 811
Reading message fails with SASL_SSL when using consumer groups #317
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
Comments
I did a bit more debugging, and have hit upon an important detail -- I am not able to reproduce this against a topic that has only one partition. By adding a |
Hi @jfancher. Thanks for the bug report, and the additional info regarding the single topic case. With that extra info, I think you've hit upon a flaw in our SASL implementation--the |
While is a breaking change for the sasl.Mechanism interface, it's not expected that library clients are implementing said interface as Kafka only accepts a very specific set of mechanisms. Fixes #317
While is a breaking change for the sasl.Mechanism interface, it's not expected that library clients are implementing said interface as Kafka only accepts a very specific set of mechanisms. Fixes #317
It still does not seem to support sasl_ssl. |
Describe the bug
We have a Kafka cluster configured to use
SASL_SSL
andSCRAM-SHA-256
. Using aDialer
configured withgb.xjqchip.workers.dev/segmentio/kafka-go/sasl/scram
, I am able to:But when I try to change the reader to use a consumer group, the fetch starts failing with an error originating from scram:
server nonce did not extend client nonce
Kafka Version
Kafka 2.1.1
To Reproduce
With a server configured as above:
This errors on the
FetchMessage
line withserver nonce did not extend client nonce
; if I remove theGroupID
from the reader config, it reads the message successfully.The text was updated successfully, but these errors were encountered: