[
https://issues.apache.org/jira/browse/KAFKA-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279359#comment-16279359
]
Vahid Hashemian commented on KAFKA-6219:
----------------------------------------
[~wenjiezhang2013] I think the issue you are experiencing is related to [this
JIRA|https://issues.apache.org/jira/browse/KAFKA-5638]. There is [a
proposal|https://cwiki.apache.org/confluence/display/KAFKA/KIP-231%3A+Improve+the+Required+ACL+of+ListGroups+API]
in place and in progress to fix this issue. Until then, your user would need a
{{Describe Cluster}} access to properly list groups.
> Inconsistent behavior for kafka-consumer-groups
> -----------------------------------------------
>
> Key: KAFKA-6219
> URL: https://issues.apache.org/jira/browse/KAFKA-6219
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 1.0.0
> Reporter: huxihx
> Assignee: huxihx
>
> For example, when ACL is enabled, running kafka-consumer-groups.sh --describe
> to describe a group complains:
> `Error: Executing consumer group command failed due to Not authorized to
> access group: Group authorization failed.`
> However, running kafka-consumer-groups.sh --list otherwise returns nothing,
> confusing user whether there are no groups at all or something wrong happened.
> In `AdminClient.listAllGroups`, it captures all the possible exceptions and
> returns an empty List.
> It's better keep those two methods consistent. Does it make any sense?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
