[
https://issues.apache.org/jira/browse/KAFKA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680417#comment-14680417
]
Parth Brahmbhatt commented on KAFKA-1695:
-----------------------------------------
[~ijuma] Don't have a date, have sent an E-mail to them.
Right now I have not included the part that depends on the release so it's not
a blocker. The APIs added in the new zkClient release are only required if we
want to set the acls on already existing zookeeper nodes. This will be the case
for anyone trying to move an existing kafka cluster to secure setup but for
fresh installation or users willing to setting the zkAcls on existing kafka
nodes manually the current patch should work as is.
> 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)
