curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <>
Subject Re: adding ACL enforcement based on ACLProvider, for consistency
Date Fri, 22 Apr 2016 14:48:26 GMT
I suggest you contact Apache about the issue. Your the first who’s mentioned any problems.
For this type of feature request, you’ll need to write the change and send a Pull Request.
A Jira issue is vital. Please keep trying and engage Apache if you continue to have trouble.


> On Apr 21, 2016, at 7:40 PM, Sergey Shelukhin <> wrote:
> Hi.
> For whatever strange reason I cannot choose Apache Curator as the project
> when creating a JIRA (I can create in other projects).
> So, I figure I¹d post it here.
> Presently, one can supply an ACLProvider when creating CuratorFramework.
> That is used to set ACLs when creating directories.
> For consistency, it would be nice to have an option to enforce the same
> ACLs for the case when the directory already exists.
> In a secure scenario, one could assume that the ACLs on his secure nodes
> would be set to whatever ACLProvider dictates; however, if someone has
> created the node before with a different ACL (say, giving themselves
> access), this assumption would be broken. As of now, the ACLs need to be
> verified or enforced manually.

View raw message