Last modified: 2007-12-07 14:22:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9364 - QISSingleSignOn Fails with MW 1.9.x/1.8.x; works great with 1.7.x/1.6.x
QISSingleSignOn Fails with MW 1.9.x/1.8.x; works great with 1.7.x/1.6.x
Product: MediaWiki extensions
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: 9389 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-03-22 03:54 UTC by duvemyster
Modified: 2007-12-07 14:22 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description duvemyster 2007-03-22 03:54:22 UTC
QISSingleSignOn fails to login existing users or create new users when applied to MW 1.9.x or 1.8.x. However, it does so 
flawless with 1.7.x and 1.6.

QISSingleSignOn utilizes AuthPlugin and $wgHooks['AutoAuthenticate'].
Comment 1 Brion Vibber 2007-03-23 14:20:49 UTC
*** Bug 9389 has been marked as a duplicate of this bug. ***
Comment 2 duvemyster 2007-04-10 00:04:33 UTC
One Solution: Comment out or remove the following lines in function QISSingleSignOnAutoAuthenticate 
in /extensions/QISSingleSignOn.php

#        if ( $user != null) {
                // user is authenticated (by another hook)
#                return true;
#        }
Comment 3 Raimond Spekking 2007-12-07 14:22:47 UTC
QISSingleSignOn is not part of SVN -> unable to apply any patch -> closing this bug as INVALID.

Note You need to log in before you can comment on or make changes to this bug.