Marketplace needs to verify that a user still controls his email account in order to convert the account to FxA. It should send an email with a verification link.
The verification link should go to an FxA login page with the email address prefilled.
I believe this is where we'll use the pre-verified API and the email will look like item #6 on the lucid chart.
Altering these bugs slightly. This is to send a pre-verification email to users once the popup has determined that the user is a verified persona user. We can use the customer-during email for this, I think the text is just right: https://github.com/mozilla/zamboni/blob/master/mkt/users/management/commands/fxa_mail.py#L15 In the lucid chart, after we send that email, we'll show a screen that looks like: https://www.dropbox.com/s/zj5nh4udbw29sbd/Screenshot%202014-09-29%2013.00.32.png?dl=0
Assignee: nobody → mstriemer
Summary: Send verification emails for transferring accounts to FxA → Send pre-verified email to users signed-out verified users
Created attachment 8500489 [details] Screenshot 2014-10-06 10.40.27.png @Maureen once the email is sent the user is notified but I'm not sure what actions they should be able to take at that point. The mockup shows a "Back" link but where does it go back to? Should the user be able to proceed to FxA without clicking the link in their email? And if so what sort of wording should we use. They'll just get a different email later so it doesn't save them anything but at least they aren't totally stuck.
Hey Ryan, can you chime in here? Thanks!
Hi gang: The Back link is only there in the event that the user has entered their email incorrectly, and needs to go back (to frame 2 or 3) to correct their email and resubmit. As per the diagram, the user will only get to the FxA Registration via the confirmation link in the email. This is because once they are at that step, they are able to change the email address (in the event they had an existing Firefox Account from Sync that is different than their original Marketplace email). Clear?
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.