Awesome, makes perfect sense thank you!
On 11/10/2017 07:28 PM, Kaufman Ng wrote:
I think "CLIENT" is just an example. The default for
listener.security.protocol.map doesn't have it. If you look at the KIP link
in my email there's a more complete example:
listener.security.protocol.map=CLIENT:
I think "CLIENT" is just an example. The default for
listener.security.protocol.map doesn't have it. If you look at the KIP link
in my email there's a more complete example:
listener.security.protocol.map=CLIENT:SASL_PLAINTEXT,REPLICATION:PLAINTEXT,INTERNAL_PLAINTEXT:PLAINTEXT,INTERNAL_SASL:SASL_P
Yep I'm familiar with that. Just curious where it's documented that, for
instance, the CLIENT listener is for client connections.
On Fri, Nov 10, 2017, 12:08 PM Kaufman Ng wrote:
> This is related to another config "listener.security.protocol.map" (since
> version 0.10.2.0). The CLIENT, PLAINTEX
This is related to another config "listener.security.protocol.map" (since
version 0.10.2.0). The CLIENT, PLAINTEXT, etc are defined as a
name-protocol mapping. So what you have in the listeners property (e.g.
CLIENT) must have an entry in the protocol map which determines which
protocol to use (e.g
I've been working with Kafka broker listeners and I'm curious is there
any documentation that explains what all of them apply to? Such as
CLIENT, PLAINTEXT, SASL/SSL, etc. I see the encryption part of the
documentation, but is it just inferred what these listeners apply to?
Thank you in advance!
