[ 
https://issues.apache.org/jira/browse/KAFKA-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Coates updated KAFKA-7011:
-------------------------------
    Description: 
Following on from the PR [#5117|[https://github.com/apache/kafka/pull/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

 

  was:
Following on from the PR [#5117|[https://github.com/apache/kafka/pull/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.


> Investigate if its possible to drop the ResourceNameType field from Java 
> Resource class.
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-7011
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7011
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: core, security
>            Reporter: Andy Coates
>            Assignee: Andy Coates
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Following on from the PR 
> [#5117|[https://github.com/apache/kafka/pull/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
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to