[KAFKA-7011] Investigate if its possible to drop the ResourceNameType field from Java Resource class.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: core, security
• Assignee: Andy Coates
• Reporter: Andy Coates
• Due: 11/Jun/18
• Created: 06/Jun/18 16:06
• Updated: 07/Jun/18 23:38
• Resolved: 07/Jun/18 23:38

Description

Following on from the PR #5117 and discussions with Colin McCabe...

 

Current placement of ResourceNameType as field in Resource class is ... less than ideal. A Resource should be a concrete resource.  Look to resolve this.

 

Thoughts...

A. I guess you could subclass Resource and have ResourcePrefix - but there is no 'is-a' relationship here and it would still allow authorise(ResourcePrefix())

B. You could move ResourceNameType into AccessControllEntryData - possible.

C. Move ResourceNameType directly into AclBinding / AclBindingFilter - possible

 

Issue Links

• links to: GitHub Pull Request #5160