[
https://issues.apache.org/jira/browse/KAFKA-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-20816.
------------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
> Add CIDR support also into Authorizer.authorizeByResourceType
> -------------------------------------------------------------
>
> Key: KAFKA-20816
> URL: https://issues.apache.org/jira/browse/KAFKA-20816
> Project: Kafka
> Issue Type: Bug
> Reporter: Maros Orsak
> Assignee: Maros Orsak
> Priority: Major
> Fix For: 4.4.0
>
>
> As reported by
> [https://github.com/apache/kafka/pull/22501#issuecomment-5021971813,] I
> didn't add support in the {{authorizeByResourceType.}}
> {{ }}
> The standard path, which goes through {{StandardAuthorizerData}} is covered
> but if someone sets up CIDR-based ACLs and an idempotent producer connects
> from an IP within the CIDR range, the authorizeByResourceType check would
> fail to match the CIDR ACL, and the producer would get
> CLUSTER_AUTHORIZATION_FAILED. It is a narrow edge case but its bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
