[KAFKA-6841] Add support for Prefixed ACLs

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: admin, security
• Assignee: Andy Coates
• Reporter: Piyush Vijay
• Reviewer: Jun Rao
• Created: 01/May/18 15:28
• Updated: 15/Jun/18 05:30
• Resolved: 15/Jun/18 05:30

Description

Kafka supports authorize access to resources like topics, consumer groups etc. by way of ACLs. The current supported semantic of resource name and principal name in ACL definition is either full resource/principal name or special wildcard '*', which matches everything.

Kafka should support a way of defining bulk ACLs instead of specifying individual ACLs.

The details for the feature are available here - https://cwiki.apache.org/confluence/display/KAFKA/KIP-290%3A+Support+for+wildcard+suffixed+ACLs

 

Issue Links

• duplicates: KAFKA-5713 Improve kafka-acls options to understand strings with wildcards
• links to: GitHub Pull Request #5079
• mentioned in: Page Loading...

Sub-Tasks

• Remove duplicate Java Resource class.: Resolved
• Remove duplicate Scala ResourceNameType class: Resolved
• Use JSON for /kafka-acl-extended-changes path: Resolved
• Consider replacing the Resource field in AclBinding with a ResourceFilter or ResourceMatcher: Resolved
• Rename ResourceNameType.ANY to MATCH: Resolved
• Investigate if its possible to drop the ResourceNameType field from Java Resource class.: Resolved