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

Setting a user as admin does not set their 6 collections #2695

Open
grantfitzsimmons opened this issue Dec 20, 2022 · 4 comments · Fixed by #3755 · May be fixed by #4652
Open

Setting a user as admin does not set their 6 collections #2695

grantfitzsimmons opened this issue Dec 20, 2022 · 4 comments · Fixed by #3755 · May be fixed by #4652
Assignees
Labels
1 - Bug Incorrect behavior of the product 2 - Security & Accounts Issues that are related to the permission system and user accounts
Milestone

Comments

@grantfitzsimmons
Copy link
Contributor

image

Found this today when I set zrogers to admin in Specify 6. I was still encountering the "no collections" warning in 6 until I unset admin, selected the collection, then selected the collections.

This is all on a local install of 6, 7, and MariaDB on macOS.

@grantfitzsimmons grantfitzsimmons added 1 - Bug Incorrect behavior of the product pri:unknown labels Dec 20, 2022
@maxpatiiuk maxpatiiuk added this to Unsorted in Users & Permissions via automation Jan 23, 2023
@grantfitzsimmons
Copy link
Contributor Author

Still a major nuisance, and potentially the cause of CSIRO's issue on Asana.

@grantfitzsimmons
Copy link
Contributor Author

A user ran into this issue today again. Something we should consider resolving sooner than later.

@CarolineDenis CarolineDenis added this to the 7.9.1 milestone Jul 10, 2023
@grantfitzsimmons grantfitzsimmons added the 2 - Security & Accounts Issues that are related to the permission system and user accounts label Jul 14, 2023
Users & Permissions automation moved this from Unsorted to Shipped Sep 26, 2023
@grantfitzsimmons
Copy link
Contributor Author

Screen.Recording.2024-03-06.at.1.20.18.PM.mov

https://umherb11024-edge.test.specifysystems.org/specify/security/user/156/?collection=4

I created the user csiro on the database umherb_1_10_24. When I set the user as an admin, I was surprised to see the collections were not set, indicating this was likely reverted during the merge.

Specify 7 System Information - 2024-03-06T19_17_40.911Z.txt

Users & Permissions automation moved this from Shipped to To do Mar 6, 2024
@grantfitzsimmons grantfitzsimmons modified the milestones: 7.9.1, 7.9.4 Mar 6, 2024
@grantfitzsimmons
Copy link
Contributor Author

Seems that it was broken already in v7.9.3
image
I set the admin role for this user, but the collection access was still not granted

@CarolineDenis CarolineDenis modified the milestones: 7.9.4, 7.9.5, 7.9.6 Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product 2 - Security & Accounts Issues that are related to the permission system and user accounts
Projects
Status: 📋 Backlog
5 participants