Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-6841 Add support for Prefixed ACLs
  3. KAFKA-7011

Investigate if its possible to drop the ResourceNameType field from Java Resource class.

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: core, security
    • Labels:
      None

      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

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                BigAndy Andy Coates
                Reporter:
                BigAndy Andy Coates
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: