Closed Bug 861221 Opened 7 years ago Closed 2 years ago
when importing Gmail contacts with two-factor auth, can't get sms from notification bar
STR: With two-factor auth enabled on you Google account: 1. run FTU 2. import Gmail contacts 3. get prompt to login to Google, and login 4. get entry field for verification code 5. see sms notification popup for a moment 6. try to pull down notification bar to get to the sms Cannot do it.
With the current window manager behaviour, any interaction with the phone during the ftu is not possible, including calls or sms. This will block probably any service with two-steps auth. If we are not gonna be able to fix it, maybe we should display a warning message when importing?
blocking-b2g: --- → tef?
not a v1.0.1. feature, moving to leo?
blocking-b2g: tef? → leo?
What would be UX recommendation for this ?
Reassigning to Francis; removing Josh and Jaime.
Product team: do we want to consider changing the FTU for this, I suspect not since we are probably considering a small portion of user who would enable 2 factor auth in the first place and there is a workaround of using the application specific passwords google provides so you don't need a sms to verify.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(ffos-product)
IMHO, we should check the percentage of users that enable that feature before planning some work here. As Fernando commented, any work here is pretty dangerous and not straight forward, unless we just want to warn the user. Cheers, F.
From a UX perspective, if we cannot fix this bug, I would suggest some alternative work-arounds. 1) Google provides the option of using application-specific passwords in those cases where 2-step authentication is required for those applications and devices that are not able to ask for verification codes. see the following video to see how this works: http://www.youtube.com/watch?v=zMabEyrtPRg&t=2m13s Would it be possible for the FTE to ask for the application-specific password rather than use the web sign-in? 2) If 1) is not possible, is there any way that we could intercept the text message, extract its contents and display it in a growl-style fixed notification above the title area? see the attached screenshot as an example
(In reply to Francis Djabri [:djabber] from comment #7) > 2) If 1) is not possible, is there any way that we could intercept the text > message, extract its contents and display it in a growl-style fixed > notification above the title area? see the attached screenshot as an example There is some work on bug 852848, regarding redirect external URIS to specific application screens. Worthy to check once it fixed.
Removing UX-P? since Francis provided UX feedback.
In the case of using an application specific password, would the user need to access gmail and set up the application specific password for the device in advance of the first run?
Triage: not willing to block on two-factor auth -- this is not the only place it's an issue on the phone and users will need to know the app-specific password workaround or wait to do the import from the Contacts app after exiting FTU. It is not a great experience but we believe it's a small portion of users who will be using two-factor, and potentially a significant amount of work to rework the FTU interface to allow for accessing SMS there.
blocking-b2g: leo? → -
(In reply to Dylan Oliver [:doliver] from comment #11) > Triage: not willing to block on two-factor auth -- this is not the only > place it's an issue on the phone and users will need to know the > app-specific password workaround or wait to do the import from the Contacts > app after exiting FTU. > > It is not a great experience but we believe it's a small portion of users > who will be using two-factor, and potentially a significant amount of work > to rework the FTU interface to allow for accessing SMS there. The product team discussed this in parallel and agrees.
As far as I can tell this is still a valid issue (albeit non-blocking.) What are the next steps here, or is this just a WONTFIX?
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.