-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Bug - Shop manager can see packages not given permission for. #3541
Comments
While defining the "Shop Manager" default group in #2183 & #2184, we only specified that it should not have the "owner" role. From @Akarshit 's research, this issue is happening because the group has "admin" role (see the "Cause" section of the issue detail). An immediate solution is to remove the "admin" role, but I think we also need to review the entire Shop Manager default group. What it stands for and it's permissions list. @spencern what are your thoughts on this? |
@impactmass @Akarshit Let's considering removing the I think restricting |
@Akarshit do you have any progress or updates for this issue? |
@spencern The fix for the issue has already been merged in |
@spencern it looks to me like this ticket was up to date? We were just waiting for |
@Akarshit @zenweasel thanks for the update, I didn't see that there was an attached PR and it was in the "in progress" column, so I wasn't sure. |
Expected behavior
Users in the
Shop Manager
group should only be able to see the packages they have been given permission for.Actual behavior
Users in the
Shop Manager
group can see all the packages(irrespective of if they have been given permission for it or not)Steps to reproduce the behavior
reaction
Cause
The cause of the issue is that the Shop Manager has admin access(here and here).
And here we say that admin can see all the packages. So even if some permission is not given to the Shop Manager, he still has the admin permission and thus would be able to see everything.
Solutions
admin
role fromShop Manager
groupadmin
users to see packages they have permission for.The text was updated successfully, but these errors were encountered: