Complete unification of all accounts to SUL
OpenPublic

Assigned To
Legoktm
Priority
Unbreak Now!
Author
MarkAHershberger
Blocks
T1382: Add login and create account links to www project portals
T24673: if last local account is moved sul should be deleted by itself
T51315: record wikibase recent change entries attributed as non-anon
T68699: Increase "remember me" login cookie expiry from 30 days to 1 year on Wikimedia wikis
T4007: Tracking bug (tracking)
T51740: watchlist filter to not show own edits doesn't work for Wikidata edits
T18690: Re-work messaging about global account status [[Special:Preferences]] once all accounts are SUL accounts
Blocked By
T70069: Set $wgCentralAuthPreventUnattached = true; on all wikis
T69995: Allow login in with pre-rename username and password
T73241: Run sendConfirmAndMigrateEmail.php for all unconfirmed emails on all wikis
T69901: Add config setting to prevent creation of new unattached accounts
T71291: Run migrateAccount.php without --safe or --auto
T72850: Not possible to filter Special:Log/gblrename by old CentralAuth account name
T70927: Prevent new account creations from taking names that have been requested in a pending rename request
T70924: Create special page to manage global rename request queue
T70886: Request global account rename from home wiki before forced SUL name change
T69350: Audit centralauth database for inconsistencies
T72392: Allow to automatically unify on login absent clashes
T74123: Add a maintenance script to send mass messages
T63876: Attach all broken autocreated local accounts to their global account
T73924: Add users_to_rename table to centralauth database
T56761: EmailableUser calls non-existing class ConfirmAndMigrateUser
T56760: sendConfirmAndMigrateEmail.php: add an option to include emailconfirmed accounts
T41817: Migrate to SUL all non-clashing accounts
T49918: Rename of global (attached) users to existing global usernames
T16862: Allow global renaming of global users
Subscribers
Asahiko, Harej, DerHexer and 50 others
Projects
Tokens
"Love" token, awarded by Ricordisamoa.
Reference
bz35707
Security
None
Description

From the (un)-archived discussion at meta (http://meta.wikimedia.org/w/index.php?title=Wikimedia_Forum&diff=next&oldid=3619272), [[User:JohnnyMrNinja]] writes (in part):

I am proposing that account unification be completed for all eligible accounts
without requiring the user to take any additional steps. This would make UL the
rule rather than the exception that it currently is, and bring us closer to the
goals of universal watchlists, recent changes, interwiki page moves, etc. This
would be especially helpful on Commons, which has so many images that were
originally uploaded at another WMF wiki, enabling better attribution without
interwiki links. I propose that it be carried out as a one-time process rather
than a continuous automatic software process, allowing users to still adjust
ULs as they see fit.

[...]what I mean by "eligible accounts" was all accounts without existing
conflicts, as these can be taken care of by an automated process. Accounts that
have conflicts would be unaffected by this specific proposal. Conflicts could
not be solved by any automated process, as each case would be different.

Looks like it has enormous support on meta. I'm not sure about the ins and outs here, so I'm going to add people who I think know more as well as post this bug to wikitech-l.


Version: unspecified
Severity: enhancement
URL: https://meta.wikimedia.org/wiki/Single_User_Login_finalisation_announcement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=39817
https://bugzilla.wikimedia.org/show_bug.cgi?id=36939

bzimport set Reference to bz35707.
MarkAHershberger created this task.Via LegacyApr 4 2012, 9:39 PM
MarkAHershberger added a comment.Via ConduitApr 4 2012, 9:55 PM

Started a thread for discussion of this on Wikitech-l: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/60388

MarkAHershberger added a comment.Via ConduitApr 6 2012, 7:07 PM

This bit was broken off of the thread but had important information: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/60484

vvv added a comment.Via ConduitApr 21 2012, 9:27 PM

Right now I do not get what specifically that user asks. I am not even sure if he understands what he is talking about. Could you elaborate, please?

bzimport added a comment.Via ConduitApr 21 2012, 11:41 PM

jsjalkgjsalga wrote:

(In reply to comment #3)

Right now I do not get what specifically that user asks. I am not even sure if
he understands what he is talking about. Could you elaborate, please?

In the past, all accounts were local. Users who still have local accounts can go to the page "Special:MergeAccount" at any WMF project whilst logged in to create an SUL account. Some users have not gone to "Special:MergeAccount" (possibly because SUL is unknown to these users). The proposal is to automatically do the "Special:MergeAccount" joining for the remaining users (as long as there are no conflicts).

I don't see why there would be issues with indefinitely locked accounts. Some of them might only have been active on one project (in which case SUL would have no advantage but also no disadvantage as the user probably wouldn't start editing at other projects anyway, and they could just register for a local account if they wanted). Other users might have been active on multiple projects, and in that case SUL would give the advantage that the users could be globally locked.

vvv added a comment.Via ConduitApr 22 2012, 12:09 AM

(In reply to comment #4)

In the past, all accounts were local. Users who still have local accounts can
go to the page "Special:MergeAccount" at any WMF project whilst logged in to
create an SUL account. Some users have not gone to "Special:MergeAccount"
(possibly because SUL is unknown to these users). The proposal is to
automatically do the "Special:MergeAccount" joining for the remaining users (as
long as there are no conflicts).

You cannot really merge accounts automatically, since you do not know whether all those users are the same users in different projects. The reason why we ask for password on Special:MergeAccount is that otherwise we cannot even check if two password hashes are the same, since they are hashed and salted (and each has a different salt).

It is true that you could look for alternative criteria of equivalence like all accounts having the same confirmed email address, or check the password and do an auto-merge on login, or merge all single-wiki accounts, but I personally do not believe that the benefits of such a feature (which are not apparent to me) would outweigh its costs of implementation.

DanielFriesen added a comment.Via ConduitApr 22 2012, 5:42 AM

(In reply to comment #5)

(In reply to comment #4)
> In the past, all accounts were local. Users who still have local accounts can
> go to the page "Special:MergeAccount" at any WMF project whilst logged in to
> create an SUL account. Some users have not gone to "Special:MergeAccount"
> (possibly because SUL is unknown to these users). The proposal is to
> automatically do the "Special:MergeAccount" joining for the remaining users (as
> long as there are no conflicts).

You cannot really merge accounts automatically, since you do not know whether
all those users are the same users in different projects. The reason why we ask
for password on Special:MergeAccount is that otherwise we cannot even check if
two password hashes are the same, since they are hashed and salted (and each
has a different salt).

It is true that you could look for alternative criteria of equivalence like all
accounts having the same confirmed email address, or check the password and do
an auto-merge on login, or merge all single-wiki accounts, but I personally do
not believe that the benefits of such a feature (which are not apparent to me)
would outweigh its costs of implementation.

This bug isn't suggesting that we automatically merge User:A on en.wp and User:A on de.wp automatically. It's suggesting that we automatically make User:A global if there is no User:A on de.wp, etc... Just like we do with new user creation.

Jarry1250 added a comment.Via ConduitSep 3 2012, 1:00 PM

Any updates on this one?

bzimport added a comment.Via ConduitMar 13 2013, 5:10 AM

wmf.amgine3691 wrote:

<blinks w00tingly>

Jdforrester-WMF added a comment.Via ConduitMay 1 2013, 3:22 AM

This doesn't remotely block bug 36939.

Noting that this is assigned to me and actually happening now.

Aklapper added a comment.Via ConduitAug 23 2013, 9:33 AM

I've lost track for when this is planned to be done and cannot find dates on https://meta.wikimedia.org/wiki/Single_User_Login_finalisation_announcement or https://meta.wikimedia.org/wiki/Help:Unified_login . Could somebody enlighten me?

Trijnstel added a comment.Via ConduitAug 23 2013, 9:39 AM

(In reply to comment #10)

I've lost track for when this is planned to be done and cannot find dates on
https://meta.wikimedia.org/wiki/Single_User_Login_finalisation_announcement
or
https://meta.wikimedia.org/wiki/Help:Unified_login . Could somebody enlighten
me?

I wondered too as I saw this change from "August 2013" to "sometime", so I asked James Forrester this week, but no reply up to now. Would love an answer.

Trijnstel added a comment.Via ConduitAug 23 2013, 9:40 AM

(In reply to comment #11)

(In reply to comment #10)
> I've lost track for when this is planned to be done and cannot find dates on
> https://meta.wikimedia.org/wiki/Single_User_Login_finalisation_announcement
> or
> https://meta.wikimedia.org/wiki/Help:Unified_login . Could somebody enlighten
> me?

I wondered too as I saw this change from "August 2013" to "sometime", so I
asked James Forrester this week, but no reply up to now. Would love an
answer.

https://meta.wikimedia.org/w/index.php?title=Single_User_Login_finalisation_announcement&diff=5726233&oldid=5643305 (sorry, forgot to add the link)

Aklapper added a comment.Via ConduitAug 26 2013, 3:32 PM

WMF's Release manager told me that this is postponed to an unknown date, as currently https://meta.wikimedia.org/wiki/HTTPS binds resources.

Nemo_bis added a comment.Via ConduitSep 4 2013, 6:59 AM

(In reply to comment #13)

WMF's Release manager told me that this is postponed to an unknown date, as
currently https://meta.wikimedia.org/wiki/HTTPS binds resources.

Thanks Greg for the update! Now that the most hectic phase of current [[m:HTTPS]] plans is over, could we get more information and maybe a little urgent work on this?

Specifically, the biggest community concern is the lack of time after notifications. The notification system was already coded and notifications don't need 100.00 % perfect lists of affected users, so sending them should require little effort and make things much, much easier in a few weeks or months when resources will be found to actually implement the change.

Stefan2 added a comment.Via ConduitOct 8 2013, 10:35 PM

(In reply to comment #14)

Thanks Greg for the update! Now that the most hectic phase of current
[[m:HTTPS]] plans is over, could we get more information and maybe a little
urgent work on this?

There is a note at [[User talk:Jdforrester (WMF)#SUL Finalisation]] which suggests that it won't take place within "the next few weeks" (as of 28 September). Also, does the information in that discussion mean that this bug is assigned to the wrong person?

Jdforrester-WMF added a comment.Via ConduitOct 8 2013, 10:40 PM

(In reply to comment #15)

Also, does the information in that discussion mean that this bug is
assigned to the wrong person?

{{fixed}}

Nemo_bis added a comment.Via ConduitOct 31 2013, 1:51 PM

I'm wondering how hard it would be for some community member to run a database query and produce a partial list of accounts which will be interested by this unification, so that we can start warning them and avoid last-minute panic. The 114,604 local accounts (as of 2013-05-16) clashing with a global accounts look like ideal candidates for a first batch of community notifications.

Aklapper added a comment.Via ConduitNov 22 2013, 3:39 PM

dgarry: Any input / opinion on Nemo's last comment? Wondering how to move forward / what is currently blocking this ticket (and bug 39817).

Aklapper added a comment.Via ConduitDec 18 2013, 2:48 PM

dgarry: Any input / opinion on Nemo's last comment? Wondering how to move
forward / what is currently blocking this ticket (and bug 39817).

Trijnstel added a comment.Via ConduitDec 18 2013, 8:53 PM

(In reply to comment #19)

dgarry: Any input / opinion on Nemo's last comment? Wondering how to move
forward / what is currently blocking this ticket (and bug 39817).

I saw something regarding global rename (and thus SUL unification) here: https://en.wikipedia.org/wiki/Wikipedia:Bureaucrats%27_noticeboard/Archive_29#CHU.2FS_.26_CHUU

Deskana added a comment.Via ConduitDec 18 2013, 9:34 PM

(In reply to comment #19)

dgarry: Any input / opinion on Nemo's last comment? Wondering how to move
forward / what is currently blocking this ticket (and bug 39817).

The blocker is basically me. I'm still new to product management and I need to sit down face to face with another product manager and be walked through this. Realistically this can't start until I'm relocated to San Francisco, which (fingers crossed) is next month.

MZMcBride added a comment.Via ConduitDec 18 2013, 9:53 PM

(In reply to comment #17)

I'm wondering how hard it would be for some community member to run a
database query and produce a partial list of accounts which will be interested
by this unification, so that we can start warning them and avoid last-minute
panic.

It would be fairly simple to generate such a list. My concern is that someone, acting in good faith, would take the list and notify tens of thousands of accounts and create a false panic, particularly before the ability to globally rename a user exists (bug 14862).

Nemo_bis added a comment.Via ConduitDec 18 2013, 10:09 PM

(In reply to comment #22)

(In reply to comment #17)
> I'm wondering how hard it would be for some community member to run a
> database query and produce a partial list of accounts which will be interested
> by this unification, so that we can start warning them and avoid last-minute
> panic.

It would be fairly simple to generate such a list. My concern is that
someone,
acting in good faith, would take the list and notify tens of thousands of
accounts and create a false panic, particularly before the ability to
globally
rename a user exists (bug 14862).

Hm? The sooner local accounts are renamed, the better.

Nemo_bis added a comment.Via ConduitMar 8 2014, 9:22 AM

Given that it's now about 7 months with no movement here, FYI I'm available to act as (volunteer) product manager for this if WMF people are too busy with other things.
It's simpler for someone with years of experience in SUL as well as local, cross-wiki and global rename practices and otherwise (stewards are another group where it's easy to find such people).

Deskana added a comment.Via ConduitMar 19 2014, 9:55 PM

I've got a plan afoot. Stay tuned for more information.

Nemo_bis added a comment.Via ConduitApr 7 2014, 6:41 PM

(In reply to Dan Garry from comment #25)

I've got a plan afoot.

I don't believe you.

Stay tuned for more information.

I don't want to stay tuned, I have limited battery. Just transmit.

bzimport added a comment.Via ConduitApr 7 2014, 7:34 PM

wmf.amgine3691 wrote:

(In reply to Dan Garry from comment #25)

I've got a plan afoot.

"Before the game is afoot, thou still let'st slip."

Deskana added a comment.Via ConduitApr 7 2014, 7:35 PM

(In reply to Nemo from comment #26)

(In reply to Dan Garry from comment #25)
> I've got a plan afoot.

I don't believe you.

Fortunately, this does not change my plans. :-)

MF-Warburg added a comment.Via ConduitApr 7 2014, 10:40 PM

And that probably means "Fortunately, this does not change my plans in any way that will result in the fixing of this bug prior to 2016." :-(

PiRSquared17 added a comment.Via ConduitJun 15 2014, 2:07 AM

(In reply to Dan Garry from comment #25)

I've got a plan afoot. Stay tuned for more information.

Bug 14862 is close to being resolved. Any news?
https://wikitech.wikimedia.org/w/index.php?title=Deployments&oldid=116060#Next_month

Scott added a comment.Via ConduitJun 16 2014, 10:34 PM

(In reply to MF-Warburg from comment #29)

And that probably means "Fortunately, this does not change my plans in any
way that will result in the fixing of this bug prior to 2016." :-(

Hey, that'll make it a nice round ten years of not being done.

https://github.com/wikimedia/mediawiki-extensions-CentralAuth/commit/f34d746dd1133f42ad878c9ad3740148d6628c41#diff-78ccdd1419c89ebda99c7fe418fc64a1

bd808 added a comment.Via ConduitJul 9 2014, 5:55 PM

Making this a proper tracking bug by blocking bug 2007 and adding the tracking keyword.

Jarry1250 added a comment.Via ConduitAug 21 2014, 10:00 PM

Just to followup re: timescales for the casual bugspam follower, it's looking more like the first quarter of 2015 for this than 2016 (source: Dan Garry).

Aklapper edited projects, added SUL-Finalization; removed Wikimedia-Site-requests.Via WebDec 2 2014, 2:21 PM
Aklapper set Security to None.
Keegan added a subscriber: Keegan.Via WebDec 5 2014, 8:44 PM
Keegan moved this task to Doing on the SUL-Finalization workboard.Via WebDec 5 2014, 8:47 PM
Pcoombe added a subscriber: Pcoombe.Via WebDec 9 2014, 7:21 PM
Glaisher mentioned this in SUL-Finalization.Via WebJan 4 2015, 4:38 PM
waldyrious added a subscriber: waldyrious.Via WebJan 14 2015, 2:14 PM
Liuxinyu970226 added a subscriber: Liuxinyu970226.Via WebJan 24 2015, 7:23 AM
-jem- added a subscriber: -jem-.Via WebJan 26 2015, 9:14 AM
Rdicerb added a subscriber: Rdicerb.Via WebFeb 3 2015, 9:18 PM
Legoktm changed the status of blocking task T73241: Run sendConfirmAndMigrateEmail.php for all unconfirmed emails on all wikis from "Stalled" to "Open".Via WebFeb 12 2015, 7:47 PM
Az1568 added a subscriber: Az1568.Via WebFeb 14 2015, 2:41 AM
jeremyb added a subscriber: jeremyb.Via WebFeb 16 2015, 3:30 AM
Ricordisamoa awarded a token.Via WebFeb 17 2015, 9:52 PM
Ricordisamoa added a subscriber: Ricordisamoa.
Shanmugamp7 added a subscriber: Shanmugamp7.Via WebFeb 19 2015, 8:37 AM
Alchimista added a subscriber: Alchimista.Via WebFeb 19 2015, 10:17 AM
KTC added a subscriber: KTC.Via WebFeb 19 2015, 1:27 PM
Eloquence added a project: Roadmap.Via WebThu, Mar 5, 7:40 AM
Eloquence moved this task to May-June 2015: Platform on the Roadmap workboard.
Jdforrester-WMF added a project: Epic.Via WebThu, Mar 5, 10:28 PM
Dcljr added a subscriber: Dcljr.Via WebFri, Mar 6, 12:29 AM
DerHexer added a subscriber: DerHexer.Via WebFri, Mar 13, 7:40 PM
Harej added a subscriber: Harej.Via WebTue, Mar 17, 6:48 AM
Asahiko added a subscriber: Asahiko.Via WebWed, Mar 18, 6:55 PM

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.