FS#22131 - {archweb} Proposal on how to create one user database for all applications
Attached to Project:
Arch Linux
Opened by Nico Schottelius (telmich) - Friday, 17 December 2010, 21:26 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 12 December 2012, 03:47 GMT
Opened by Nico Schottelius (telmich) - Friday, 17 December 2010, 21:26 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 12 December 2012, 03:47 GMT
|
Details
Description:
This is a proposal on how a migration to one database for users could be done: http://www.nico.schottelius.org/blog/archlinux-single-authentication-database/ |
This task depends upon
Closed by Dan McGee (toofishes)
Wednesday, 12 December 2012, 03:47 GMT
Reason for closing: Won't implement
Additional comments about closing: This isn't happening.
Wednesday, 12 December 2012, 03:47 GMT
Reason for closing: Won't implement
Additional comments about closing: This isn't happening.
* Define what a fix is: Delete or merge or rename or whatever
That is still the insurmountable obstacle... We can not just deleting/renaming accounts.
In this case the only change that may happen to the user is that only of out of 4 passwords can be used in the migration.
In case of a conflict and the users are definitely different users (I assume those are only very little), one can either rename
one or for fairness reasons both accounts. One could even consider renaming using suffixes of the system, like telmich_bugtracker,
which also states the origin.
I understand that this is not beautiful, but neither is the current situation.
This may be a step that must be taken, if there should be one user database.
I wouldn't investigate too much into this topic until it's clear how many conflicts are there, which cannot be resolved easily,
because of disjunct foreign keys (like realname, email, url, whatever).
As for the transition, it would be easier with a service specifically available to manage accounts. Users could start creating new accounts with this system, then have the option to tie old accounts with the old authentication to their new accounts, thus importing the data.
How this will all work, I haven't the slightest idea, but I do agree that this seems like a reasonable request.