[
https://issues.apache.org/jira/browse/ZOOKEEPER-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko resolved ZOOKEEPER-3969.
-----------------------------------------
Fix Version/s: (was: 3.6.3)
Resolution: Fixed
Issue resolved by pull request 1504
[https://github.com/apache/zookeeper/pull/1504]
> Add whoami API and Cli command
> -------------------------------
>
> Key: ZOOKEEPER-3969
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3969
> Project: ZooKeeper
> Issue Type: New Feature
> Reporter: Mohammad Arshad
> Assignee: Mohammad Arshad
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.7.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> When connected to Zookeeper through CLI, many times there is need to know who
> is the current user. This is helpful when finding ACL related problems.
> Finding who is current user is not easy, have to check many configuration
> both at client and at server.
> Personally I run below three commands to know the current user
> {code:java}
> create /a
> setAcl /a auth::cdrwa
> getAcl /a
> {code}
> Given all the above facts, I think adding whoami command will be good add-on
> into the zookeeper command list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
