Community
Participate
Working Groups
When a committer changes their email address via site login we presently only update their Ldap record and Bugzilla. However other places also need this update: Gerrit,IPzilla,Mailman,Foundation and possibly Wiki and the Forums. -M.
I've done forums from bug 353872.
Marketplace
*** Bug 408131 has been marked as a duplicate of this bug. ***
I guess this would affect the Forges' instances of the services too.
(In reply to comment #4) > I guess this would affect the Forges' instances of the services too. Um, yup.
I just want to make sure I understand the problem. We need to come up with a patch for the drupal site login to merge an account when the user made a change to his email address? I am assuming that right now, it's creating a new user in the drupal database.
(In reply to comment #6) > I just want to make sure I understand the problem. > > We need to come up with a patch for the drupal site login to merge an > account when the user made a change to his email address? > > I am assuming that right now, it's creating a new user in the drupal > database. If we are doing a user_load_by_name when loading the user, than I think we're ok. The next time a user login the email / first / last will be updated from the Friends class.
(In reply to comment #6) > I just want to make sure I understand the problem. [snip] > I am assuming that right now, it's creating a new user in the drupal > database. Not just in Drupal -- every other piece of software we run maintains its own user table: Bugzilla, Forums, Marketplace, Wiki, Gerrit, etc. If email changes do not update the user tables in those applications, a new user account is created when someone logs in. And as Thanh mentions, now that authentication is centralized for all the forges, multiply all that by three (for now). If the drupal Site Login is handling email changes, those should perhaps go in the account_requests table so that we can update all the other sources.
> When a committer changes their email address via site login we presently > only update their Ldap record and Bugzilla. However other places also need > this update: Gerrit,IPzilla,Mailman,Foundation and possibly Wiki and the > Forums. > And as Thanh mentions, now that authentication is centralized for all the > forges, multiply all that by three (for now). It becomes clear to me that all these updates should be handled by our Community Creator. Since it's run on each forge and it pulls data from the same account tables, we can tune it to tweak local auth settings stored on each forge from one central location. > If the drupal Site Login is handling email changes, those should perhaps go > in the account_requests table so that we can update all the other sources. Nathan, Chris ... Is it?
Target for 2014 Q1. This is really annoying.
(In reply to Denis Roy from comment #8) > user table: Bugzilla, Forums, Marketplace, Wiki, Gerrit, etc. If email Bugzilla: updates Forum: updates Marketplace: does not update Wiki: updates Gerrit: updates EclipseCon: does not update IPZilla: does not update Mailman: does not update PMI: does not update Foundation: updates
(In reply to Denis Roy from comment #11) > (In reply to Denis Roy from comment #8) > > user table: Bugzilla, Forums, Marketplace, Wiki, Gerrit, etc. If email > > Bugzilla: updates > Forum: updates > Marketplace: does not update > Wiki: updates > Gerrit: updates > EclipseCon: does not update > IPZilla: does not update > Mailman: does not update > PMI: does not update > Foundation: updates Denis, let's talk about this in our next weekly meeting. I am curious to know how you are dealing with this on the wiki, forum and bugzilla. Maybe you have something that we could leverage with drupal?
> Denis, let's talk about this in our next weekly meeting. I am curious to > know how you are dealing with this on the wiki, forum and bugzilla. SELECT id FROM table WHERE email = $oldemail UPDATE table SET email = $newemail WHERE id = $id LIMIT 1 addLogEntry("Winning");
As we've casually discussed, we simply update values in the SQL databases. I suspect we can do the same with the various Drupals. It is, however, one point worthy of consideration: each and every time we enable some site (or software) that maintains local copies of user data, we have to sync it.
> PMI: does not update on dbmaster.projects update users set mail = "new" where users.name = "id";
*** Bug 314404 has been marked as a duplicate of this bug. ***
When the user changes his eclipse account e-mail and then logs in to marketplace or another drupal site, a new account is created. Do we need to create some kind of account merging tool or should we only update e-mail addresses going forward? We should also verify if an account already exist before updating the user table for a drupal site. In drupal, it's possible for an admin to manually create an account for a user before the user update his e-mail address.
(In reply to Christopher Guindon from comment #17) > When the user changes his eclipse account e-mail and then logs in to > marketplace or another drupal site, a new account is created. > > Do we need to create some kind of account merging tool or should we only > update e-mail addresses going forward? > > We should also verify if an account already exist before updating the user > table for a drupal site. > > In drupal, it's possible for an admin to manually create an account for a > user before the user update his e-mail address. Our drupal site_login module handle this now.
Chris, I think this can be closed?
(In reply to Denis Roy from comment #19) > Chris, I think this can be closed? All Drupal sites update email addresses on user login and with a cron job for users that don't login to each of our sites. Matt can you confirm that LCC is updating email addresses for Gerrit, IPzilla, Mailman, Foundation, Wiki and the Forums?
(In reply to Christopher Guindon from comment #20) > Matt can you confirm that LCC is updating email addresses for Gerrit, > IPzilla, Mailman, Foundation, Wiki and the Forums? Yes, all of those are updated on Eclipse.org when an email address changes. The forges(and related services) are not updated, so those are still a sticking point. However with the plan to eventually fold those services back into Eclipse.org it may be moot. -M.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
(In reply to Eclipse Webmaster from comment #21) > (In reply to Christopher Guindon from comment #20) > > > Matt can you confirm that LCC is updating email addresses for Gerrit, > > IPzilla, Mailman, Foundation, Wiki and the Forums? > > Yes, all of those are updated on Eclipse.org when an email address changes. > > The forges(and related services) are not updated, so those are still a > sticking point. However with the plan to eventually fold those services > back into Eclipse.org it may be moot. > > -M. Closing
