The creation of 3rd party apps around the current API is hindered by the fact such apps would need to store user credentials. The adoption of the MediaWiki API is limited to knowledgeable MediaWiki developers and highly experienced Wikipedia users. A completely different interface could be used, tailored to particular user needs.
![mediawiki oauth mediawiki oauth](https://user-images.githubusercontent.com/290496/48671968-2c316080-eb73-11e8-9e6a-9e895cd67262.png)
The write API inspires the idea of editing Wikimedia via something other than MediaWiki. With some rare exceptions, though, API-based write access is only used by bots. This means you can edit, change and interact with MediaWiki's contents without using the MediaWiki interface. MediaWiki has an API providing read/write access to its database. Please chime in on the Talk Page.Ĭommunications Background Probably the biggest question right now is whether this feature should go in core or be developed as an extension.
MEDIAWIKI OAUTH CODE
![mediawiki oauth mediawiki oauth](https://workingwithmediawiki.com/book/images/Block%20interface.png)
This protocol does not reveal usernames or passwords to the third-party tool. OAuth provides a standard protocol to negotiate secure access tokens and to provide third-party tools (web or client) with granular access to private resources. This page is superseded, check out Auth systems for updates.