It seems to be already opened
https://issues.apache.org/jira/browse/KAFKA-15513
Il giorno ven 3 nov 2023 alle ore 16:18 Jesus Cea ha scritto:
> What version of Kafka are you using? I am testing 3.6.0.
>
> Do you have an account to open an issue at
> https://issues.apache.org/jira/projects/KAFKA/
On 3/11/23 16:45, Richard Bosch wrote:
I haven't worked with KRaft controllers in SASL mode yet, but could I think
that the early.start.listeners might help here. (
https://kafka.apache.org/documentation/#brokerconfigs_early.start.listeners)
It was meant to indicate that these listeners are depen
YesX.509 client certificates
kafka_2.13-3.6.0.tgz
Il giorno ven 3 nov 2023 alle ore 16:04 Jesus Cea ha scritto:
> On 3/11/23 11:25, Daniele Carminati wrote:
> > But, when i try to enable SCRAM/SASL on controller -> controller
> > i get this error
> > [2023-11-03 09:05:02,134] INFO [SocketSer
I haven't worked with KRaft controllers in SASL mode yet, but could I think
that the early.start.listeners might help here. (
https://kafka.apache.org/documentation/#brokerconfigs_early.start.listeners)
It was meant to indicate that these listeners are depending on data in the
cluster itself for bo
What version of Kafka are you using? I am testing 3.6.0.
Do you have an account to open an issue at
https://issues.apache.org/jira/projects/KAFKA/issues/?
Thanks
--
Jesús Cea Avión _/_/ _/_/_/_/_/_/
j...@jcea.es - https://www.jcea.es/_/_/_/_/ _/_/
On 3/11/23 11:25, Daniele Carminati wrote:
But, when i try to enable SCRAM/SASL on controller -> controller
i get this error
[2023-11-03 09:05:02,134] INFO [SocketServer listenerType=CONTROLLER,
nodeId=1] Failed authentication with /192.168.1.34
(channelId=192.168.1.33:9093-192.168.1.34:56006-130
