I'm working at development of LrMediaWiki, a plug-in for Adobe Photoshop Lightroom which enables Lightroom users to upload images to a MediaWiki instance inside the application. Users need to login to upload images, user's login credentials are stored by the plug-in. Recently I detected deprecated MediaWiki API calls related to the login. According to the methods recommended at API:Login, I decided to use the API action "clientlogin" for future versions of LrMediaWiki to resolve the deprecated issues. I'm not sure, if this decision was right. Maybe, the "login" action might fit better to LrMediaWiki, but it seems this supports only bot users/passwords, not main accounts. LrMediaWiki needs to support both kinds of credentials: (a) normal main accounts and (b) bot users/passwords. Up to now, my changes (using "clientlogin" action) resolved the deprecated issues with main accounts, but bot users/passwords don't work. Testing bot users/passwords with a non-WMF MediaWiki 1.28.0 instance yields an error message "The supplied credentials could not be authenticated." (If $wgLanguageCode set to "de": "Die angegebenen Anmeldeinformationen konnten nicht überprüft werden.") Testing bot users/passwords with commons.wikimedia.beta.wmflabs.org running MediaWiki 1.29.0-alpha results to an error message "Incorrect password entered. Please try again." Therefore I assume, API action "clientlogin" doesn't support bot users/passwords. Any idea, how I could support both kinds of credentials?
Topic on Project:Support desk/Flow
API:Login is written a little awkwardly. I think the main thing for you is this bit: "Interactive applications such as mobile apps that aim to completely replace access to the web-based user interface should use the clientlogin action to authenticate."
LrMediaWiki is an application that the user uses instead of the website. This seems to match "Interactive applications... that aim to completely replace access to the web-based user interface."
Mark, thanks for your contribution!
In the meantime I adressed this issue at API talk:Login#Support of both kinds of credentials?. The response I got there helped me to fix the issue. Therefore this thread here can be treated to be resolved and can be closed.