Repository navigation
fix(kafka): add strimzi-no-tls and redpanda-no-tls providers - #181
Merged
Merged
Conversation
Self-hosted Strimzi or Redpanda can run SASL without TLS. No provider key covered this. `strimzi` derives SASL_SSL. Every client using it on that listener failed with a transport error. Consumers kept their own provider table. Both keys derive SASL_PLAINTEXT with SCRAM-SHA-512. SCRAM is challenge-response, so the password never crosses the plaintext transport. No PLAIN or OAUTHBEARER provider gets such a key. KnownProvider adds both as self-hosted KRaft providers. The Redpanda provider has the Redpanda schema registry. The strict DEFAULT_ALLOWED set leaves them out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Self-hosted Strimzi or Redpanda can run SASL without TLS. No provider key covered this.
strimziderives SASL_SSL. Every client using it on that listener failed with a transport error.Consumers kept their own provider table.
Both keys derive SASL_PLAINTEXT with SCRAM-SHA-512. SCRAM is challenge-response, so the password never crosses the plaintext transport. No PLAIN or OAUTHBEARER provider gets such a key.
KnownProvider adds both as self-hosted KRaft providers. The Redpanda provider has the Redpanda schema registry. The strict DEFAULT_ALLOWED set leaves them out.