Skip to content

Comments

feat(kafka): implement SCRAM-SHA-256/512 authentication support#724

Open
jpedrosa94 wants to merge 1 commit intoethpandaops:masterfrom
jpedrosa94:feat/kafka-scram-authentication
Open

feat(kafka): implement SCRAM-SHA-256/512 authentication support#724
jpedrosa94 wants to merge 1 commit intoethpandaops:masterfrom
jpedrosa94:feat/kafka-scram-authentication

Conversation

@jpedrosa94
Copy link

@jpedrosa94 jpedrosa94 commented Jan 10, 2026

Description

Fixes incomplete SCRAM authentication implementation in Kafka output. The code accepted SCRAM configuration but didn't implement the actual SCRAM protocol handler, causing authentication failures.

Changes

  • Add scramClient implementation for SASL SCRAM authentication
  • Set SCRAMClientGeneratorFunc for SCRAM-SHA-256 and SCRAM-SHA-512 mechanisms
  • Add xdg-go/scram dependency for SCRAM protocol handling
  • Add documentation for SASL authentication configuration in sentry, cannon, and mimicry docs
  • Add SCRAM-SHA-512 configuration examples

Testing

  • Tested successfully against production Kafka broker with SCRAM-SHA-512 authentication
  • Built and deployed forked Docker image (juliopedrosa/xatu:scram-fix) to our environment for validation

Background

We needed SCRAM authentication for our Kafka infrastructure and discovered the existing implementation was incomplete. Created a forked Docker image with this fix that we're currently running in our environment.

Related Issues

Fixes issue where Kafka output with SCRAM mechanisms would fail to authenticate despite correct configuration. #726

- Add scramClient implementation for SASL SCRAM authentication
- Set SCRAMClientGeneratorFunc for SCRAM-SHA-256 and SCRAM-SHA-512
- Add xdg-go/scram dependency for SCRAM protocol handling
- Fix incomplete SCRAM support that only accepted config but didn't implement protocol
- Add documentation for SASL authentication in sentry, cannon, and mimicry docs
- Add SCRAM-SHA-512 configuration examples
@jpedrosa94 jpedrosa94 requested a review from Savid as a code owner January 10, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant