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 plugin #1994

Open
dasari008 opened this issue Aug 1, 2024 · 2 comments
Open

RBAC plugin #1994

dasari008 opened this issue Aug 1, 2024 · 2 comments
Labels
jira kind/bug Something isn't working status/triage

Comments

@dasari008
Copy link

dasari008 commented Aug 1, 2024

RBAC Policy to allow every user read access does not work

I have installed the RBAC plugin and defined a default policy using a csv file. I'm not quite familiar with Casbin rule format but i think the policy i have defined here states that i want to allow every user the read action for the catalog-entity read resource.

p, *, catalog-entity, read, allow

Expected Behavior

The permission catalog-entity.read is denied for the user user:default/<my-username>

What are the steps to reproduce this bug?

Install the rbac backend plugin and set the policy as defined above in a csv file.

The app-config.local yaml file

permission:
   enabled: true
   rbac:
     pluginsWithPermissions:
        - catalog
        - scaffolder
        - permission
     policies-csv-file:  <absolute-path-of-the-csv-file-where-the-policy-is-defined>
     admin:
        superUsers:
           -name:  user:default/<some-other-username>

Versions of software used and environment

Local development
Node 18
Backstage version 1.29

@dasari008 dasari008 added kind/bug Something isn't working status/triage labels Aug 1, 2024
@github-actions github-actions bot added the jira label Aug 1, 2024
@PatAKnight
Copy link
Member

Sorry, we do not have support for wildcards at the moment. To be able to add the permission catalog.entity.read to your user user:default/<my-username>, you will need to create a role that can then be added to that permission.

g, user:default/<my-username>, role:default/some-role
p, role:default/some-role, catalog-entity, read, allow

Some more examples can be found here

@dasari008
Copy link
Author

@PatAKnight No issues and thanks for letting me know. The issue is that assigning individual users to a role is very tiresome process when we have thousands of users. I see this issue here is what i'm also looking for. Hopefully we will have this feature in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira kind/bug Something isn't working status/triage
Projects
None yet
Development

No branches or pull requests

2 participants