You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Andras Katona (Jira)" <ji...@apache.org> on 2022/04/07 02:55:00 UTC
[jira] [Updated] (RANGER-3231) Ranger should use kafka Authorizer from KIP-504
[ https://issues.apache.org/jira/browse/RANGER-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Katona updated RANGER-3231:
----------------------------------
Fix Version/s: 3.0.0
> Ranger should use kafka Authorizer from KIP-504
> -----------------------------------------------
>
> Key: RANGER-3231
> URL: https://issues.apache.org/jira/browse/RANGER-3231
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Ismael Juma
> Assignee: Andras Katona
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: ranger_kafka.zip
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As described in the KIP, `org.apache.kafka.server.authorizer.Authorizer` is an improvement over `kafka.security.auth.Authorizer` and it's a pure Java interface (instead of Scala).
> `kafka.security.auth.Authorizer` has been deprecated since December 2019 and it will be removed in Apache Kafka 3.0 (roughly planned for July/August).
> See the KIP for more details:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-504+-+Add+new+Java+Authorizer+Interface
--
This message was sent by Atlassian Jira
(v8.20.1#820001)