-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
type/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug
Description
Search before asking
- I searched in the issues and found nothing similar.
Version
Pulsar 2.9.3
Minimal reproduce step
- Set up a pulsar cluster with
topicLevelPoliciesEnabled=true. - Create a namespace
t1/n1and set admin roletenant_adminas the admin of tenantt1. - Create topic
t1/n1/t1and use roletenant_adminto produce/consumer this topic. DO NOT GRANT the permissions oftenant_adminto the topic/namespace. - Update the namespace/topic policy, such as grant another role
role1with produce to topict1/n1/t1. - We can see the producers/consumers of role
tenant_adminwill all first disconnect and then reconnect.
What did you expect to see?
All producers and consumers should be stable.
What did you see instead?
The producers/consumers of role tenant_admin will all first disconnect and then reconnect.
Anything else?
According to the logic in org.apache.pulsar.broker.service.ServerCnx, all permission check will go to org.apache.pulsar.broker.authorization.PulsarAuthorizationProvider#allowTopicOperationAsync, which means the tenant admin should be the super user of all namespace/topic under specific tenant.
Are you willing to submit a PR?
- I'm willing to submit a PR!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
type/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug