Feature summary:
I would like pywikibot to be able to run when provided an OAuth2 access token, maybe per request.
Use case(s):
It would allow writing a webservice that authenticates using OAuth2 and then passing the token to a function.
Benefits:
It would make it possible to run scripts via OAuth2.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | • Bstorm | T246122 Upgrade the Toolforge Kubernetes cluster to v1.16 | |||
| Resolved | • Bstorm | T211096 PAWS: Rebuild and upgrade Kubernetes | |||
| Open | None | T192237 Support administrative actions in PAWS | |||
| Open | None | T243200 Move PAWS to OAuth 2.0 | |||
| Open | Xqt | T418997 Add support for new global API limits | |||
| Open | Feature | Xqt | T323849 pywikibot: Support OAuth2 token |
Note that in the future what we'd like to recommend for bots is OAuth 2 client credentials (so rather than storing an access token in the configuration, you store the client ID and secret, and then the bot can use some standard OAuth library to fetch a new access token every few hours). It's not actually supported yet, though.
T407987: Define best practice for single-user apps which need a high MediaWiki API rate limit has more context.
I would postpone it until client credentials flow is implemented upstream,
See https://api.wikimedia.org/wiki/Authentication
Implemtation of owner-only-tokens is proposed
https://www.mediawiki.org/wiki/OAuth/Owner-only_consumers#OAuth_2