Hi! I was trying to triage tickets for the wwwfpo kanban on GitLab and noticed I've no access at all when logged in... I'm not even listed in the group members list: https://gitlab.com/groups/fedora/design/-/group_members
I wonder if it's related to some of the FAS group changes @ryanlerch was looking at doing for the Design Team. @nirik had the idea that maybe i needed to detach Fedora SAML and reattach it to my account to have it refresh the FAS groups, so I did that, and ended up in the situation jflory hit here: https://pagure.io/fedora-infrastructure/issue/10755
Note that this created a rogue "duffy3" GitLab account with my Fedora creds! So I checked and when i was logged in with this rogue duffy3 account, I was at least listed (as non SAML) in the members list for the design team group. It seemed I didn't really have permissions to do what I needed though (changing labels on issues for issue triaging.)
I was able to delete the rogue / ghost account and reattach SAML to a fresh session of my real GitLab account, but now I am no longer listed in the group membership list again. So I don't think the theory of logging the account out and back into SAML was the issue. Any ideas?
It's a pretty big blocker for me to not be able to triage and update the wwwfpo design tickets.
Some things that might be helpful to know: - My FAS username is duffy - My GitHub username is mairin - The FAS group for the design team is designteam - The FAS group for design team admins is designteam-admin
Here is the thread / background on the recent changes in FAS / GitLab for this team: https://discussion.fedoraproject.org/t/fedora-design-gitlab-permissions/39546/2
Just to update the ticket: I manually added them and permissions seem to persist, so I guess the immediate issue is solved, however, its unclear to me why it happened in the first place. ;(
@ryanlerch any ideas? Or should we just close this and hope it never happens again?
@ryanlerch got this all sorted from what I understand.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.