krishvishal opened a new issue, #4528: URL: https://github.com/apache/iggy/issues/4528
## Summary The gateway closes the connection for a SaslHandshake v0 client, Produce below v3 and Fetch below v4. Kafka 4.0 dropped the same versions (KIP-896), but Kafka 3.x clusters still serve them. Who hits it: - With SASL on: Sarama up to 1.40.1, which sends SaslHandshake v0 by default. kafka-python 2.0.2, which always sends v0 and was the latest release for four and a half years. aiokafka up to 0.12, with `api_version="auto"`. - Version pins below Kafka 0.11 in Sarama, kafka-python and aiokafka. Tutorials and Event Hubs threads recommend such pins. - Sarama below 1.46, pinned at V2_8 or later, sends Metadata v10 and gets closed. #4527 removes this case. librdkafka 1.8.0, which Ubuntu 22.04 ships, works, because the gateway advertises the old minimums. ## Scope - [ ] SaslHandshake v0 with the SASL tokens that follow it without a Kafka header (before KIP-152) - [ ] On request only: message formats v0 and v1, converted to v2 on Produce and Fetch ## Acceptance criteria - [ ] kafka-python 2.0.2 and Sarama 1.40.1 authenticate with SASL PLAIN, then produce and consume -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
