[
https://issues.apache.org/jira/browse/KAFKA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-1695:
-------------------------------
Status: In Progress (was: Patch Available)
Setting this to in-progress because it doesn't include tests and changes may be
required to make that possible.
> 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
> Fix For: 0.9.0.0
>
>
> 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)
