Vision:
The principal authorizing an action is clearly modeled and readily available in code.
Developers can check user permissions in a concise and clear way.
Permission checks or rate limits applied by application logic can easily be tested.
Please review the initiative vision and vote here: https://www.mediawiki.org/wiki/Core_Platform_Team/Initiatives/Authority
See also: T231930: Introduce Authority objects to represent the user performing a given action
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T273514 MW expedition work [high effort] | |||
| Open | None | T262296 Authority [high effort] | |||
| Resolved | • Pchelolo | T261963 Spike to explore Authority concept, implementation, and migration | |||
| Resolved | • Pchelolo | T271458 RevisionRecord should use Authority for permission checks | |||
| Resolved | • Pchelolo | T271300 Stop using the global service locator in RevisionRecord::userCanBitfield | |||
| Resolved | • Pchelolo | T271459 User should implement Authority |
@Naike: Hi, the Due Date set for this open task was four months ago. Can you please either update or reset the Due Date (by clicking ), or set the status of this task to resolved via the Add Action... → Change Status dropdown in case that this task is done? Thanks.
@Naike: Due Date was six months ago so I removed it. Please keep Due Dates updated - thanks.