Last modified: 2014-11-17 09:21:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T11604, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9604 - Get OpenID extension to a state where it could be used on Wikimedia projects as a provider (tracking)
Get OpenID extension to a state where it could be used on Wikimedia projects ...
Status: ASSIGNED
Product: MediaWiki extensions
Classification: Unclassified
OpenID (Other open bugs)
unspecified
All All
: Normal enhancement with 22 votes (vote)
: ---
Assigned To: Ryan Lane
http://www.mediawiki.org/wiki/Extensi...
: tracking
: 27428 (view as bug list)
Depends on: 34357 44438 45914 46258 51331 53087 54509 54510 54512 54677 56254 56660 57579 57 3060 17637 18528 44165 44293 44353 44416 44821 45304 45308 46053 46617 54413 54506 54507 54508 54511 57065 57478 57578
Blocks: tracking 13631 59631 23735
  Show dependency treegraph
 
Reported: 2007-04-17 10:56 UTC by Anon Sricharoenchai
Modified: 2014-11-17 09:21 UTC (History)
18 users (show)

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


Attachments

Description Anon Sricharoenchai 2007-04-17 10:56:11 UTC
According to, http://bugzilla.wikimedia.org/show_bug.cgi?id=3060
and, http://bugzilla.wikimedia.org/show_bug.cgi?id=57

This extension would be great and help the bug #57 to be partially fixed.

OpenID is an distributed open Single-Sign-On System targeted on forums, wikis,
weblogs etc.

The extension is available at:
http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/OpenID/

The documentation is at:
http://www.mediawiki.org/wiki/Extension:OpenID
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-04-17 16:28:53 UTC
My understanding is that this will be on the drawing board once the framework
for bug 57 is in place, and it will not be considered before then.  Changing
dependency accordingly.
Comment 2 Théo 2007-05-01 12:54:21 UTC
Well, bug 57 seems unsolvable.
My idea of "How OpenID on Wikipedia should work" :
 * create a sub-domain for hosting OpenID accounts ( eg. id.wikimedia.org)
 * create your openID on id.WM.org
 * link your OpenID and your "local account" (double confirmation, with OpenID
and local accounts)
 * use your OpenID (where you have not a "local account") and your local account
(where you have one)

In fact, your unique OpenID and yours local accounts are attached.
Comment 3 Mike.lifeguard 2008-10-22 01:58:59 UTC
(In reply to comment #2)
> Well, bug 57 seems unsolvable.
> My idea of "How OpenID on Wikipedia should work" :
>  * create a sub-domain for hosting OpenID accounts ( eg. id.wikimedia.org)
>  * create your openID on id.WM.org
>  * link your OpenID and your "local account" (double confirmation, with OpenID
> and local accounts)
>  * use your OpenID (where you have not a "local account") and your local account
> (where you have one)
> 
> In fact, your unique OpenID and yours local accounts are attached.

Well, bug 57 has been solved now.
Comment 4 Mike.lifeguard 2009-03-19 17:16:09 UTC
Do we know if the code is ready for use?
Comment 5 SJ 2009-05-04 20:24:38 UTC
Good question.  I'd like to be able to use my WM identity elsewhere.
Comment 6 Alexandre Emsenhuber [IAlex] 2009-06-19 11:27:26 UTC
Added bug 17637 as dependency for this bug since for now OpenID extension only supports "FileStore" storage, which would need access through NFS.
Comment 7 Betacommand 2009-08-07 19:16:26 UTC
remove shell keyword not ready for shell yet
Comment 8 ipatrol 2010-05-31 16:40:19 UTC
I would say this is good, but we shouldn't give full user privileges because we can't apply account creation blocks as effectively and, as our Wikipedia article says, there is a higher phishing risk. I would suggest limiting the privileges to user, non-autoconfirmed, and give them a username as idusername@providername. Full privileges simply require creating a local username and password.
Comment 9 Jan Kucera (Kozuch) 2010-07-30 09:22:21 UTC
Related reading:
http://strategy.wikimedia.org/wiki/Proposal:Support_OpenID
Comment 10 Chad H. 2011-02-15 12:49:10 UTC
*** Bug 27428 has been marked as a duplicate of this bug. ***
Comment 11 Siebrand Mazeland 2011-05-16 09:54:36 UTC
Mass maintainer change.
Comment 12 T. Gries 2011-05-28 20:42:00 UTC
For those who want to test, the present version in trunk (OpenID 0.929-beta) works ***very*** well. If someone gives me the possibility to install it on a WMF wiki, please let me know.
Comment 13 T. Gries 2012-08-15 19:33:31 UTC
removed blocker. It does not "block" the Provider property.
Comment 14 T. Gries 2012-08-15 19:34:22 UTC
see also Wikimedia as OpenID Provider https://bugzilla.wikimedia.org/show_bug.cgi?id=13631
Comment 15 Tyler Romeo 2012-08-16 13:24:09 UTC
(In reply to comment #8)
> I would say this is good, but we shouldn't give full user privileges because we
> can't apply account creation blocks as effectively and, as our Wikipedia
> article says, there is a higher phishing risk. I would suggest limiting the
> privileges to user, non-autoconfirmed, and give them a username as
> idusername@providername. Full privileges simply require creating a local
> username and password.

Are these limitations still applicable? If so why? (I cannot seem to find the article mentioned explaining why.)
Comment 16 Ryan Kaldari 2013-01-29 21:51:38 UTC
There's currently a proposal on the English Wikipedia village pump to turn on OpenID. Is there any reason (technical or practical) that this wouldn't be feasible?
Comment 17 T. Gries 2013-01-29 22:20:53 UTC
(In reply to comment #16)
> There's currently a proposal on the English Wikipedia village pump to turn on
> OpenID. Is there any reason (technical or practical) that this wouldn't be
> feasible?

I am currently working on an improved version, so an implementation should wait until the new version is code reviewed and committed (perhaps in 2 weeks).
Comment 18 Tyler Romeo 2013-01-29 22:32:09 UTC
Also, there are a number of open bugs that make E:OpenID in its current form impossible to deploy functionally to WMF.
Comment 19 Ryan Lane 2013-01-30 06:35:56 UTC
Does the village pump specify as a consumer or a provider? We'll need a designer to fix the UX issues to use it as a consumer. There's a number of bugs in the provider code, though Thomas is working on them.
Comment 21 T. Gries 2013-02-27 23:17:23 UTC
assigned to the master
Comment 22 James Forrester 2013-05-24 07:57:27 UTC
Making this clearer per comments on bug 13631.

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


Navigation
Links