#51703 closed enhancement (fixed)
Add fine grained capabilities for managing app passwords
Reported by: | TimothyBlynJacobs | Owned by: | TimothyBlynJacobs |
---|---|---|---|
Milestone: | 5.7 | Priority: | normal |
Severity: | normal | Version: | 5.6 |
Component: | Application Passwords | Keywords: | granular-capabilities has-patch has-unit-tests |
Focuses: | rest-api | Cc: |
Description
Currently, app passwords check the edit_user
meta capability. Ideally, we'd introduce a set of more fine grained capabilities for managing app passwords. This might be as simple as an manage_app_passwords
meta cap that follows the same mapping as edit_user
, or we could be more fine-grained and have list_app_passwords
, create_app_passwords
, etc...
Change History (10)
This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.
4 years ago
This ticket was mentioned in Slack in #core-restapi by hellofromtonya. View the logs.
4 years ago
This ticket was mentioned in PR #917 on WordPress/wordpress-develop by TimothyBJacobs.
4 years ago
#6
- Keywords has-patch has-unit-tests added
Trac ticket: https://core.trac.wordpress.org/ticket/51703
TimothyBJacobs commented on PR #917:
4 years ago
#8
Thanks for the review! Great point, I've deprecated it in 9972c38.
#9
@
4 years ago
- Owner set to TimothyBlynJacobs
- Resolution set to fixed
- Status changed from new to closed
In 50114:
Watching because I'm interested to see if there are any good alternatives to introducing new primitive caps.
If it is time to introduce new primitive caps (perhaps in a "staggered" way so that a DB upgrade is not needed), the privacy component and media are also sorely in need of new caps, so co-ordination on this would be great.