{"action":"opened","issue":{"url":"https://api.github.com/repos/mozilla/addons-server/issues/6451","repository_url":"https://api.github.com/repos/mozilla/addons-server","labels_url":"https://api.github.com/repos/mozilla/addons-server/issues/6451/labels{/name}","comments_url":"https://api.github.com/repos/mozilla/addons-server/issues/6451/comments","events_url":"https://api.github.com/repos/mozilla/addons-server/issues/6451/events","html_url":"https://github.com/mozilla/addons-server/issues/6451","id":258796068,"number":6451,"title":"Allow FxA to update user's email address without the using logging in","user":{"login":"eviljeff","id":768592,"avatar_url":"https://avatars2.githubusercontent.com/u/768592?v=4","gravatar_id":"","url":"https://api.github.com/users/eviljeff","html_url":"https://github.com/eviljeff","followers_url":"https://api.github.com/users/eviljeff/followers","following_url":"https://api.github.com/users/eviljeff/following{/other_user}","gists_url":"https://api.github.com/users/eviljeff/gists{/gist_id}","starred_url":"https://api.github.com/users/eviljeff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eviljeff/subscriptions","organizations_url":"https://api.github.com/users/eviljeff/orgs","repos_url":"https://api.github.com/users/eviljeff/repos","events_url":"https://api.github.com/users/eviljeff/events{/privacy}","received_events_url":"https://api.github.com/users/eviljeff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-19T12:04:32Z","updated_at":"2017-09-19T12:04:32Z","closed_at":null,"author_association":"MEMBER","body":"FxA allows a second email address to be added to an FxA account, and will soon allow that second email address to be made the primary, effectively allowing the user to change their email address. (See https://bugzilla.mozilla.org/show_bug.cgi?id=1393588 for more background.)\r\n\r\nAMO updates the email address, if changed, on login, so we will get the new email next time they log in to AMO.  But in the meantime AMO has the old email address so we may then be emailing incorrectly about editor reviewers, user reviews, admin matter, etc.\r\n\r\nQuestion: could one of the existing API endpoints be trivially used to allow this?  /authenticate  and /login both do the update.  But also both mark the user as having logged in.  (And are there additional state and tokens that FxA wouldn't have?)\r\n\r\nOtherwise, we need a special endpoint just for FxA.\r\n\r\n"}}
{"actor":{"display_login":"eviljeff"}}