Re: Kafka SASL (Kerberos) - UNKNOWN_TOPIC_OR_PARTITION

2018-08-20 Thread Matt L
te: > is auto topic creation enabled on server? Any deny logs in > kafka-authorizer.log? > What is the inter-broker protocol configured? If it is SSL, SSL user should > have ClusterAction permission. > > On Mon, Aug 20, 2018 at 3:33 PM Matt L wrote: > > > Hello, > > &g

Kafka SASL (Kerberos) - UNKNOWN_TOPIC_OR_PARTITION

2018-08-20 Thread Matt L
Hello, Having trouble when publishing and consuming from a topic with SASL_PLAINTEXT. Both ZK and Kafka start successfully, in logs I see SASL_PLAINTEXT on 9093 as being available. kafka.log:[2018-08-20 03:31:08,202] INFO Registered broker 1 at path /brokers/ids/1 with addresses: EndPoint(kafkab

Restrict access on kafka with multiple listener

2018-07-18 Thread Matt L
Hi, I have an existing Kafka Cluster that is configured as PLAINTEXT. We want to enable SASL (GSSAPI) as an additional listener. Is there a way to force specific topics to only accept traffic (pub/con) from a certain listener? e.g. if i create a topic and set ACLS, how do i stop a client from us

Re: Restrict access on kafka with multiple listener

2018-07-17 Thread Matt L
Hi, I have an existing Kafka Cluster that is configured as PLAINTEXT. We want to enable SASL (GSSAPI) as an additional listener. Is there a way to force specific topics to only accept traffic (publish/consume) from a certain listener? e.g. if i create a topic and set ACLS, how do i stop a client