In MobileFrontend we have support for requesting cross domain tokens using centralauth token. We've had to use this code for Wikigrok work and are likely to need it gain.
To kill MobileFrontend we should move this api code to a more logical place. As @Legoktm rightly points out core is not necessarily the right place for this, but CentralAuth may be.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T158181 Aim for workflow equivalence for MediaWiki on desktop and mobile web | |||
| Resolved | Jdlrobson | T71366 [EPIC] Extract Minerva skin from MobileFrontend to its own repository | |||
| Resolved | hoo | T50389 [Bug] Login issue with add language links widget | |||
| Resolved | Jdlrobson | T110102 Completely remove api.js and ForeignApi.js, their functionality has been upstreamed | |||
| Resolved | matmarex | T66636 Upstream ForeignAPI code in MobileFrontend into core/CentralAuth |
Mobile's ForeignAPI handles more than just CentralAuth (and its 'centralauthtoken'), it also handles the usual cross-origin AJAX woes. I think we could try splitting it into mw.ForeignApi (which would extend mw.Api and live in core), and mw.CentralAuthForeignApi (which would extend mw.ForeignApi and live in CentralAuth).
So the problem is that we want any code to be able to just depend on mw.ForeignApi and not need to worry about whether CentralAuth or any other auth-related extension is installed. If we did it like I suggested above, then every RL module wishing to use cross-wiki API, and handle both CentralAuth-enabled and other wikis, would have to be conditionally registered with different dependency (either mw.CentralAuthForeignApi or mw.ForeignApi).
Here's how we could solve it:
Change 231710 had a related patch set uploaded (by Bartosz Dziewoński):
Introduce mediawiki.ForeignApi
Change 231711 had a related patch set uploaded (by Bartosz Dziewoński):
Implement a mediawiki.ForeignApi extension
Not quite resolved. We'll need to remove the code in MobileFrontend :) I'll put that on my to do!
Change 233631 had a related patch set uploaded (by Jdlrobson):
ForeignApi module should target mobile
Change 233631 merged by jenkins-bot:
mediawiki.ForeignApi: Module should target mobile
I have written/expanded https://www.mediawiki.org/wiki/Manual:CORS#Using_mediawiki.ForeignApi to document the new feature and linked it in a few places on mw.org.
I think this should be included in Tech News. Proposed wording: Gadget writers can now use [[Manual:CORS#Using_mediawiki.ForeignApi|mediawiki.ForeignApi]] to easily communicate between different Wikimedia wikis. (This task is still open, but this part is implemented and can be announced anytime.)
It seems that we're handling this as T110102 (patch pending), so I'll mark this one as closed again.
@Johan A question or maybe I am asking for an elucidation of the subject name here and the text that appeared in the Tech News
Gadget writers can now use mediawiki.ForeignApi to communicate between different Wikimedia wikis.
To me the ticket talks about login details and interconnectivity of a login. For the tech news it reads more about the broader interaction/interoperability between the wikis, eg. crosswiki transclusion. Of course, it may be that ForeignAPI has a jargon that is very tight that represents something to coders than to the broader public. The clarification would be useful. Thanks.
Better late reply than never:
This is only a JavaScriot interface, it does not allow for cross-wiki transclusion or anything. But it does allow you to write a gadget to, say, update the description page of a file on Commons with a new translation directly from a Wikipedia article; or to write a gadget to update all references to a file on all Wikipedias after it is moved on Commons; or to upload a file to Commons directly from the editor (something we're working on at Multimedia); or to synchronise your user preferences from the central wiki to all other ones; and so on. (This was possible before, if you were determined; now it is easy and hopefully people will create such things.)