Last modified: 2014-09-11 18:51:17 UTC
CentralAuth's Special:GlobalGroupMembership (aka Special:GlobalUserRights) only allows users to use it who are already in a global group that confers the 'globalgroupmembership' right -- no local group can apply this property. While this sounds nice, it seems to involve a bit of a chicken-and-egg problem: without diving into the raw database, there's nobody who can add the first global op user to the appropriate group. Bug 17308 requests entirely *removing* the global right and replacing it with *only* a local right, for a different reason -- ensuring that it can only be run from a single wiki. This appears to be motivated by logging issues -- apparently we don't (or didn't, don't know the current status) have global logs for global actions like this, so the logs go into the local wiki where they might not be seein. Either way, it would be useful to have some way to actually set it in the first place...
migrateStewards.php does that.
migrateStewards.php isn't necessarily going to be run -- if you start your wiki on CentralAuth to begin with, you have nothing to migrate.
vasilvv: You're set as assignee here, do you plan to work on this or should the assignee be reset to default? (And the ticket has "high priority" set for nearly three years which might be unrealistic)
No, and I don't actually believe that this is a serious issue. Bootstrapping CentralAuth is not something which really happens often (it probably happens mostly in dev environment -- and developers can deal with command-line tools and direct database access).
*** Bug 43916 has been marked as a duplicate of this bug. ***
*** Bug 31897 has been marked as a duplicate of this bug. ***
