Hi,
I am using MediaWiki 1.28.
I want users to authenticate using OpenID Connect so I have deployed the
PluggableAuth and OpenID Connect extensions and they are working well.
I also want to provision accounts in my wiki from another system of record
using the API and so I have deployed the OAuth extension, created an
owner-only OAuth consumer, and have written a PHP client against the
API. It too is working well.
The issue is that in order for the PHP client to leverage the API and
authenticate using OAuth AND for users to authenticate using OpenID
Connect I need to set
$wgPluggableAuth_EnableLocalLogin = true;
If I do not set that then the PHP client cannot authenticate using
OAuth.
Have I missed something so that I would not have to enable local login
in order for the PHP client to use OAuth to authenticate and leverage
the API to provision accounts?
If not, then I am satisfied with the solution I have except for the user
login experience. I want them to click "Log in" but not have to then see
the Special:UserLogin page.
My thought is to replace that special page with one I create with a
custom extension that extends the SpecialUserLogin class as suggested
here:
http://stackoverflow.com/questions/42776926/how-do-you-edit-the-html-for-me…
Is that the simplest and most elegant approach, or is there a cleaner
way to "hide" the Username/Password form from users and avoid them
having to click twice to start the OpenID Connect flow?
Thanks,
Scott K
I want to develop a browser extension to save the text of all submitted
revisions to the local machine.
So for example, suppose you are editing a wiki and you click "save". Your
browser would then save a copy of that revision on your hard drive. Then
you would have all those submissions saved as backups, which could be
helpful if your article were to be deleted or if the wiki were to go down.
There's a problem on the Internet in general, which is that when sites go
down, the content is often irretrievably lost because no one archived it.
This could be a way to help fight against that, by making it easier for
authors to keep copies at least of their own work (which is probably some
of the content they care most about and would be most interested in
salvaging and reposting elsewhere).
I'm thinking this should probably be a Firefox and/or Brave extension,
since those browsers seem the most compatible with MediaWiki. Any
suggestions on what's the best way to go about this? Do you know of any
other browser extensions/plugins I might be able to cannibalize or use as
inspiration for this? Thanks.
But I don't *HAVE* a LocalSetting.php file yet. This happens either when I
do a "git clone/composer update" install, or a vanilla "tarball/extract"
install. I hit up http://mysite.dev/mw-config/index.php, and it dutifully
reports that:
MediaWiki 1.28.1
LocalSettings.php not found.
Please complete the installation <http://mysite.dev/mw-config/index.php> and
download LocalSettings.php.
But on the page following it errors out with:
A LocalSettings.php file has been detected. To upgrade this installation,
please enter the value of $wgUpgradeKey in the box below. You will find it
in LocalSettings.php.
Installer be crazy.
I've cleared my cache, used a different browser, erased the ~/.composer
directory, deleted the directory/tried again and various combinations of
trying to "reset" this, but I'm still prompted with the error.
Occasionally, though, I run across this error too:
*Fatal error*: Class 'ComposerAutoloaderInit_mediawiki_vendor' not found in
*/usr/local/www/wiki/vendor/autoload.php* on line *7*
Does anyone have an idea of what might be causing this?
--
Andrius