[ZOOKEEPER-2779] Add option to not set ACL for reconfig node

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 3.5.3
• Fix Version/s: 3.7.0, 3.5.8
• Component/s: server
• Labels: pull-request-available
• Assignee: Jordan Zimmerman
• Reporter: Jordan Zimmerman
• Created: 09/May/17 14:03
• Updated: 11/May/20 15:41
• Resolved: 29/Mar/20 20:05

Description

ZOOKEEPER-2014 changed the behavior of the /zookeeper/config node by setting the ACL to ZooDefs.Ids.READ_ACL_UNSAFE. This change makes it very cumbersome to use the reconfig APIs. It also, perversely, makes security worse as the entire ZooKeeper instance must be opened to "super" user while enabled reconfig (per ReconfigExceptionTest.java). Provide a mechanism for savvy users to disable this ACL so that an application-specific custom ACL can be set.

Issue Links

• links to: GitHub Pull Request #248
• links to: GitHub Pull Request #248
• links to: GitHub Pull Request #249
• links to: GitHub Pull Request #249