Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
From: hanm <git@git.apache.org>
To: dev@zookeeper.apache.org
Reply-To: dev@zookeeper.apache.org
References: <git-pr-282-zookeeper@git.apache.org>
In-Reply-To: <git-pr-282-zookeeper@git.apache.org>
Subject: [GitHub] zookeeper issue #282: ZOOKEEPER-1782: Let a SASL super user be super
Content-Type: text/plain
Message-Id: <20170622185936.54E30DFB30@git1-us-west.apache.org>
Date: Thu, 22 Jun 2017 18:59:36 +0000 (UTC)
archived-at: Thu, 22 Jun 2017 18:59:38 -0000

Github user hanm commented on the issue:

    https://github.com/apache/zookeeper/pull/282
  
    `zookeeper.superUser` was added in ZOOKEEPER-938 and it was never documented. I doubt people even know about this property without looking into source code and/or the description of ZOOKEEPER-938, but I agree compatibility concern here is very reasonable. 
    
    So let's stick to `zookeeper.superUser` for this patch. We can give it a shinny name later. The only remaining work is to document this `zookeeper.superUser`. The doc source is located https://github.com/apache/zookeeper/blob/master/src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml, search `zookeeper.DigestAuthenticationProvider.superDigest` or `X509AuthenticationProvider.superUser` as references of existing superuser documents.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---