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:SASL_PLAINTEXT,REPLICATION:PLAINTEXT,INTERNAL_PLAINTEXT:PLAINTEXT,INTERNAL_SASL:SASL_PLAINTEXT
advertised.listeners=CLIENT://cluster1.foo.com:9092
,REPLICATION://broker1.replication.local:9093,INTERNAL_PLAINTEXT://broker1.local:9094,INTERNAL_SASL://broker1.local:9095
listeners=CLIENT://192.1.1.8:9092,REPLICATION://10.1.1.5:9093
,INTERNAL_PLAINTEXT://10.1.1.5:9094,INTERNAL_SASL://10.1.1.5:9095
On Fri, Nov 10, 2017 at 7:10 PM, Thomas Stringer <trstrin...@gmail.com>
wrote:
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 <kauf...@confluent.io> wrote:
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. CLIENT:SASL_PLAINTEXT).
The idea is that the same protocol can be used in multiple listeners. For
example you might have SASL/SSL in two listeners (different network
interface or port).
This is part of KIP-103, you can see more details there:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-
103%3A+Separation+of+Internal+and+External+traffic
On Fri, Nov 10, 2017 at 10:10 AM, Thomas Stringer <trstrin...@gmail.com>
wrote:
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!
--
Kaufman Ng
+1 646 961 8063
Solutions Architect | Confluent | www.confluent.io
