Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

[Schema Registry] Force authorization when kafkaEnableMultiTenantMetadata is false #1807

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Commits on Jul 14, 2023

  1. [Schema Registry] Force authorization when kafkaEnableMultiTenantMeta…

    …data is false
    
    ### Motivation
    
    Currently when the schema registry and authorization are both enabled,
    the authorization is only performed when
    `kafkaEnableMultiTenantMetadata` is false. It's not reasonable because
    the role of the token must have the write permission to the schema
    registry topic.
    
    ### Modifications
    
    - In `performAuthorizationValidation`, do not chec
      `kafkaEnableMultiTenantMetadata`.
    - Add the `testSchemaWrongAuth` to verify that a wrong role cannot be
      used to create an Avro produce.
    - Separate the default namespace and the default schema namespace in
      `KafkaAuthorizationTestBase` so that the permission requirements
      will be clear.
    BewareMyPower committed Jul 14, 2023
    Configuration menu
    Copy the full SHA
    fcde386 View commit details
    Browse the repository at this point in the history