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

[jira] [Commented] (KAFKA-2641) Upgrade path for ZK authentication

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

Gwen Shapira commented on KAFKA-2641:
-------------------------------------

I hope that the patch will include updates to the upgrade documentation and not just the necessary code :)

> Upgrade path for ZK authentication
> ----------------------------------
>
>                 Key: KAFKA-2641
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2641
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Flavio Junqueira
>            Assignee: Flavio Junqueira
>
> If a cluster isn't secure and wants to migrate to secure, then it will need to execute the following steps with respect to ZK:
> # Perform a rolling restart passing the appropriate JAAS file to enable the ZK client to authenticate against the server 
> # Run a ZkSecurityMigrationTool that will set the appropriate ACLs 
> # Perform a second rolling restart to set `zookeeper.enable.secure.acls`
> This recipe assumes that the ZK ensemble has security on. 



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