[jira] [Commented] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

["Mohammed amine GARMES (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15639763#comment-15639763 ] 

Mohammed amine GARMES commented on KAFKA-3469:
----------------------------------------------

Hello, 
I spent much time with this problem before I find this discussion, maybe you can clarify this point in your documentation :

http://kafka.apache.org/090/documentation.html#security_sasl 

Indeed, we need to use the same principal in the "Zookeeper client authentication" configuration for all workers 

// Zookeeper client authentication
    Client {
       com.sun.security.auth.module.Krb5LoginModule required
       useKeyTab=true
       storeKey=true
       keyTab="/etc/security/keytabs/kafka_server.keytab"
       principal="kafka/zkadmin@EXAMPLE.COM";
    };

bests regards

> kafka-topics lock down znodes with user principal when zk security is enabled.
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-3469
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3469
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ashish K Singh
>            Assignee: Ashish K Singh
>
> In envs where ZK is kerberized, if a user, other than user running kafka processes, creates a topic, ZkUtils will lock down corresponding znodes for the user. Kafka will not be able to modify those znodes and that leaves the topic unusable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)