[
https://issues.apache.org/jira/browse/KAFKA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527365#comment-16527365
]
ASF GitHub Bot commented on KAFKA-7028:
---------------------------------------
stanislavkozlovski opened a new pull request #5311: KAFKA-7028: Properly
authorize custom principal objects
URL: https://github.com/apache/kafka/pull/5311
Previously, it would compare two different classes `KafkaPrincipal` and the
custom class, which would always return false because of the implementation of
`KafkaPrincipal#equals`
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
