You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
@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.
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 useruser: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
Versions of software used and environment
Local development
Node 18
Backstage version 1.29
The text was updated successfully, but these errors were encountered: