ah okay that makes sense. also explains why for a distributed source i
actually has to set it twice:
security.protocol=SASL_PLAINTEXT
producer.security.protocol=SASL_PLAINTEXT
if anyone runs into this issue and just wants it to work... this is what is
in my configs now:
security.protocol=SASL_PLAI
Koert,
I think what you're seeing is that there are actually 3 different ways
Connect can interact with Kafka. For both standalone and distributed mode,
you have producers and consumers that are part of the source and sink
connector implementations, respectively. Security for these are configured
well it seems if you run connect in distributed mode... its again
security.protocol=SASL_PLAINTEXT and not producer.security.protocol=
SASL_PLAINTEXT
dont ask me why
On Thu, Nov 24, 2016 at 10:40 PM, Koert Kuipers wrote:
> for anyone that runs into this. turns out i also had to set:
> producer.
for anyone that runs into this. turns out i also had to set:
producer.security.protocol=SASL_PLAINTEXT
producer.sasl.kerberos.service.name=kafka
On Thu, Nov 24, 2016 at 8:54 PM, Koert Kuipers wrote:
> i have a secure kafka 0.10.1 cluster using SASL_PLAINTEXT
>
> the kafka servers seem fine, and
i have a secure kafka 0.10.1 cluster using SASL_PLAINTEXT
the kafka servers seem fine, and i can start console-consumer and
console-producer and i see the message i type in the producer pop up in the
consumer. no problems so far.
for example to start console-producer:
$ kinit
$ export KAFKA_OPTS=
