[
https://issues.apache.org/jira/browse/KAFKA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527322#comment-16527322
]
Rajini Sivaram commented on KAFKA-7028:
---------------------------------------
[~enether] Let's not depend on {{equals()}} from custom classes since we need
to be able to instantiate custom principal objects from Strings to make that
work. And that needs a KIP.
We could either instantiate a {{KafkaPrincipal}} from the (type, name) of the
custom principal as [~hachikuji] has suggested or directly check the type and
name instead of calling {{equals()}}. It is probably easiest to instantiate a
{{KafkaPrincipal}} at the start of {{authorize()}} and use that everywhere so
that {{superUsers.contains()}} as well as the ACL checks work. [~enether] What
do you think?
> super.users doesn't work with custom principals
> -----------------------------------------------
>
> Key: KAFKA-7028
> URL: https://issues.apache.org/jira/browse/KAFKA-7028
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Stanislav Kozlovski
> Priority: Major
> Fix For: 2.1.0
>
>
> SimpleAclAuthorizer creates a KafkaPrincipal for the users defined in the
> super.users broker config. However, it should use the configured
> KafkaPrincipalBuilder so that it works with a custom defined one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
