Closed
Bug 1073571
Opened 11 years ago
Closed 11 years ago
[Email] If user has setup 2 step verification they cannot manually add gmail account
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
INVALID
People
(Reporter: rkunkel, Unassigned)
Details
(Whiteboard: [2.1-Daily-Testing])
Attachments
(1 file)
91.33 KB,
text/plain
|
Details |
Description:
If the user has an existing gmail account with 2 step verification enabled, they are unable to manually add that account to their email app. If they go through the automatic account setup however, they are prompted for their secondary passcode and the account is added successfully.
Setup Steps:
1) Create a gmail account with 2 step verification enabled
Repro Steps:
1) Update a Flame device to BuildID: 20140926000202
2) Connect to WiFi or cellular data
3) Launch the Email app
4) Attempt to add the gmail account with 2 step verification manually
Actual:
User is unable to add account manually
Expected:
User add the account manually
Environmental Variables:
Device: Flame 2.1
BuildID: 20140926000202
Gaia: 6a6ed9433fce47e76c07fd35bc5952acb108f4c8
Gecko: 7b09a378588c
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Repro frequency: 100%
See attached: logcat
Reporter | ||
Comment 1•11 years ago
|
||
This issue also affects the latest 2.2 Flame KK build:
Enviromental Variables:
----------------------------------------
Device: Flame 2.2 Master
BuildID: 20140926040203
Gaia: a06714c555ca7068545f10b4437a16c14cd8e7f5
Gecko: 9e3d649b80a2
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
User is unable to manually add a gmail account with 2 step verification enabled.
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(pbylenga)
Whiteboard: [2.1-Daily-Testing]
Comment 2•11 years ago
|
||
qawanted for branch checks to see if this is a regression.
Comment 3•11 years ago
|
||
This is operating as intended. The log indicates that an attempt was made to use the user's general password instead of an application-specific password. We removed the specific error message that tells the user to use an application-specific password when we introduced support for use of XOAuth2 via autoconfig (on both v2.1 and v2.2). Our autoconfig mechanism is resilient for gmail/google-hosted domains through the use of MX lookups and so manual config should not be required. If someone wants to use manual config to setup their gmail-hosted account and they have 2-factor auth configured, they need to know to use an application-specific password too.
You need to log in
before you can comment on or make changes to this bug.
Description
•