Red Hat Bugzilla – Bug 431346
user accounts not picking up inherited permissions
Last modified: 2013-06-23 22:25:58 EDT
qa_whiteboard, editbugs, and setpriority are all inherited permissions in the
bugzilla sense of the word from being in fedora_contrib from my understanding.
However, new contributors that are inserted into fedora_contrib via FAS are not
picking up these inherited permissions until an admin looks at the user, then
the user magically gets the permissions. Note this conversation on IRC (jds2001
== me, abadger1999 == Toshio Kuratomi, ianweller == a user that was having issues):
23:21 < abadger1999> ianweller: and open up this page and tell me what's there:
23:22 < ianweller> abadger1999: fedora_contrib is the only one listed
23:22 < abadger1999> ianweller: Okay. Looking
23:23 < abadger1999> ianweller: Refresh that page please
23:23 < abadger1999> Tell me if you have all four permissions now
23:24 < ianweller> i have all four now yes.
23:24 < ianweller> thanks :)
23:24 < jds2001> abadger1999: what did you do?
23:24 < abadger1999> jds2001: I think we're dealing with a quantum mechanical
23:24 < jds2001> lol
23:25 < abadger1999> If I look at the permissions in the admin page they
suddenly get the proper permissions.
23:25 < jds2001> hmmm
23:25 < abadger1999> (I don't change anything. Just look the user up and then
click onto their page to see what's there.)
I tested this issue and yes the permissions of the user don't get updated until
an admin views the user's page using editusers.cgi, basically this issue is
caused by updating user's permissions using the xmlrpc function
Admin.updatePerms(), the function is missing couple of lines to refresh and
derive the user's groups after updating their permissions, editusers.cgi has
those lines that is why the permissions gets refreshed there. attaching a patch
with the fix for a review.
Thanks for reporting the issue.
a patch to fix this problem has been committed to cvs , it should be live when
the next bugzilla package is pushed to production which on the latest will be
This change is not on production server. Please reopen if there are any problems.
"not" or "now"? I assume the latter.
now for sure lol.