You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2015/08/10 14:25:46 UTC

[jira] [Commented] (KAFKA-1695) Authenticate connection to Zookeeper

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

Ismael Juma commented on KAFKA-1695:
------------------------------------

[~parth.brahmbhatt], do you know when the new release for `zkClient` wil be out? Do I understand correctly that it's a blocker for this work? Trying to figure out if we should be targetting this for 0.8.3.

> Authenticate connection to Zookeeper
> ------------------------------------
>
>                 Key: KAFKA-1695
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1695
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Jay Kreps
>            Assignee: Parth Brahmbhatt
>
> We need to make it possible to secure the Zookeeper cluster Kafka is using. This would make use of the normal authentication ZooKeeper provides. ZooKeeper supports a variety of authentication mechanisms so we will need to figure out what has to be passed in to the zookeeper client.
> The intention is that when the current round of client work is done it should be possible to run without clients needing access to Zookeeper so all we need here is to make it so that only the Kafka cluster is able to read and write to the Kafka znodes  (we shouldn't need to set any kind of acl on a per-znode basis).



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