Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RBAC: prefixed subjects for schema registry ACLs don't work #375

Closed
egarjans opened this issue Nov 1, 2021 · 1 comment
Closed

RBAC: prefixed subjects for schema registry ACLs don't work #375

egarjans opened this issue Nov 1, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@egarjans
Copy link

egarjans commented Nov 1, 2021

Describe the bug
Adding prefixed ACL for schema registry subjects doesn't work.

Example descriptor file:

---
context: "context"
source: "source"
projects:
  - name: "foo"
    schemas:
      - principal: "User:alice"
        subjects:
          - "tests*"

For "User:alice" i added ACLs using Julie OPS, but "User:barnie" i added manually through Confluent Control Center
Result is below:

root@tools:/# confluent iam rolebinding list --kafka-cluster-id $KAFKA_ID --schema-registry-cluster-id $SR_ID --principal User:alice
  Principal  |     Role      | ResourceType |      Name      | PatternType
+------------+---------------+--------------+----------------+-------------+
  User:alice | ResourceOwner | Subject      | Subject:tests* | LITERAL
root@tools:/# confluent iam rolebinding list --kafka-cluster-id $KAFKA_ID --schema-registry-cluster-id $SR_ID --principal User:barnie
   Principal  |     Role      | ResourceType | Name  | PatternType
+-------------+---------------+--------------+-------+-------------+
  User:barnie | ResourceOwner | Subject      | tests | PREFIXED

Runtime (please complete the following information):

  • OS: RHEL 8.4
  • Docker version 20.10.7
  • docker-compose version 1.29.2
  • JVM version: openjdk version "11.0.11" 2021-04-20
  • Version 3.2.0
@purbon
Copy link
Collaborator

purbon commented Nov 21, 2021

Hi @egarjans, thanks a lot for your report. This issue should be solved with the merge of #405, core of the problem here was an incorrect resource naming by when this resource was created.

Thanks a lot.

@purbon purbon closed this as completed Nov 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants