OAuth and bot passwords (and maybe other things, now that grants are in core) rely on $wgGrantPermissions to expose access to privileged functionality, but most extensions don't support it. Any extensions that defines a user right which can in some way influence use of the API should also create a grant for that right, or add it to some existing grant.
Description
Description
Event Timeline
Comment Actions
User groups are assigned to users. Grants are assigned to tools. When a tool acts through a user account, it will only have those rights which are available both through the user's groups and the tool's grants.
Comment Actions
Hello @Tgr, I have both config set now but I still have the missing key error!
$wgOAuth2PrivateKey = "/Users/hannah/Development/core/my_ssh"; $wgOAuth2PublicKey = "/Users/hannah/Development/core/my_ssh.pub";
Token request failed with HTTP 500: {"error":"server_error","error_description":"The authorization server encountered an unexpected condition which prevented it from fulfilling the request: Key cannot be empty","message":"The authorization server encountered an unexpected condition which prevented it from fulfilling the request: Key cannot be empty"}Comment Actions
That's the UBN from earlier this week (T416456). You'll need to update OAuth and/or MediaWiki core and re-run Composer.