[
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354676#comment-15354676
]
Rakesh R commented on ZOOKEEPER-1045:
-------------------------------------
Yes, exactly. We need to ensure that the addition of this feature shouldn't
introduce any compatibility issues whoever is upgrading from old {{3.4.x}}
version to the new {{3.4.x'}}. All the existing functionality should work fine
with (1) the feature is disabled, (2) during rolling upgrade steps, (3) after
the successful upgrades with feature enabled.
There will be many combinations like below. All these may not be the actual
deployment cases but to be on the safer side we could consider it while
reviewing/testing.
||client-server||server-server||
|No Auth|No Auth(disabled)|
|Sasl Auth|No Auth(disabled)|
|No Auth|Sasl Auth|
|Sasl Auth|Sasl Auth|
> Support Quorum Peer mutual authentication via SASL
> --------------------------------------------------
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: Eugene Koontz
> Assignee: Rakesh R
> Priority: Critical
> Fix For: 3.4.9, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch,
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip,
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf,
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch,
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch,
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers.
> This bug, on the other hand, is for authentication among quorum peers.
> Hopefully much of the work done on SASL integration with Zookeeper for
> ZOOKEEPER-938 can be used as a foundation for this enhancement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
