[ https://issues.apache.org/jira/browse/KAFKA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527280#comment-16527280 ]
Stanislav Kozlovski commented on KAFKA-7028: -------------------------------------------- As far as I can tell, checking the type and name would be the easiest and quickest fix to this problem. Since the comparison with the type and a name was made explicit in the KIP and approved, I assume it makes sense. Otherwise another option would be to let users override `equals()` on their custom class and use that, but that would require us to instantiate the custom principal on the broker as well. Seeing as this problem hasn't been reported for almost a year, I assume the demand for that is low > 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)