Description
Related Objects
- Mentioned Here
- T434063: Remove partial revocation feature from OAuth grant management UI
T409901: TypeError: array_keys(): Argument #1 ($array) must be of type array, null given by $resourceServer->getScopes()
T413947: Updating grants (via Special:OAuthManageMyGrants) of OAuth accepted consumers overrides its grants with empty array
Event Timeline
OTOH without access to that screen, they can't even see what grants the application has. I think the link should be unconditional, and then maybe there shouldn't be an update button if no meaningful changes can be made.
Yes, this makes sense. I think this should also extend to non-authonly consumers that have only basic rights as well?
There seems to be an overlap between "authonly" consumers (authonly and authonlyprivate) and "non-authonly" consumers with only basic rights (useoauth). The overlap is that these are the default rights applied, and I'm wondering if it would make sense to also not have access to the "Update grants" button in the latter case. So I'm thinking of unifying the experience of these management workflows.
But for consumers who have more grants (outside the defaults), we can display the "Update grants" button for grant management. Let me know what you think.
I'd probably decline this in favor of T434063: Remove partial revocation feature from OAuth grant management UI.