Found I still hit this issue without VPN. I had to make the cluster's user
a super user or at least give it appropriate privileges
On Thu, Aug 4, 2016 at 11:39 AM Bryan Baugher wrote:
> Figured this out. This had to do with me being on a VPN and running
> everything locally
>
> On Thu, Aug 4, 20
Figured this out. This had to do with me being on a VPN and running
everything locally
On Thu, Aug 4, 2016 at 11:26 AM Bryan Baugher wrote:
> I managed to replicate this issue using the default provided config for
> kafka/zookeeper in the binary artifact and using the console producer to
> write
I managed to replicate this issue using the default provided config for
kafka/zookeeper in the binary artifact and using the console producer to
write a message
On Thu, Aug 4, 2016 at 10:23 AM Bryan Baugher wrote:
> Using the --producer option in kafka-acls.sh it looks to have allowed
> create o
Using the --producer option in kafka-acls.sh it looks to have allowed
create operations on the cluster. Turning on trace logging for
authorization shows repeated mentions of my user and that its allowed to
create on the cluster and describe the topic.
Looks like I might not be the only one with th
Hi,
Can you enable Authorization debug logs and check for logs related to
denied operations..
we should also enable operations on Cluster resource.
Thanks,
Manikumar
On Thu, Aug 4, 2016 at 1:51 AM, Bryan Baugher wrote:
> Hi everyone,
>
> I was trying out kerberos on Kafka 0.10.0.0 by creating
Hi everyone,
I was trying out kerberos on Kafka 0.10.0.0 by creating a single node
cluster. I managed to get everything setup and past all the authentication
errors but whenever I try to use the console producer I get 'Error while
fetching metadata ... LEADER_NOT_AVAILABLE'. In this case I've crea
