Closed Bug 996248 Opened 11 years ago Closed 7 years ago

[FxAccounts] Move refreshAuthentication test from IAC-API TestFXA app to RP-API UITest app

Categories

(Firefox OS Graveyard :: FxA, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: njpark, Unassigned)

Details

(Whiteboard: [fxa4fxos2.0])

No description provided.
STR: - Log in to Firefox Accounts, and the use the FxA Test app and click 'Refresh Authentication UI' - Enter the correct password. - (Alternatively) enter the wrong password: Expected: - The dialog that shows the correct workflow should be displayed. Actual: - 'The user is already signed in' message shows. Version Info: │ Gaia f3abbd2d0a60f1a1618db93f8b1957cae6de379c │ │ Gecko https://hg.mozilla.org/mozilla-central/rev/215080b813a7 │ │ BuildID 20140414040203 │ │ Version 31.0a1
Assignee: nobody → spenrose
Blocks: 989363
No longer blocks: 996101
I believe that we have no plans to exercise refreshAuthentication through the IAC API in the 2.0 timeframe. refreshAuth will be used by FMD and possible Marketplace via navigator.mozId, and will work* once bug 994934 lands (i.e. sometime today). Logout, which does use the IAC API, does not require forceAuth** (see bug 949100 ). I therefore propose that we close this issue by removing the refreshAuthentication functionality from the TestFxA app. Jared and Jed? * except that right now a failed challenge DOES log you out, which contradicts the user stories. I'll file a follow-up bug. ** forceAuth is just refreshAuth with a grace period of 0.
Flags: needinfo?(jparsons)
Flags: needinfo?(6a68)
(In reply to Sam Penrose from comment #2) > I therefore propose that we close this issue by removing the > refreshAuthentication functionality from the TestFxA app. Jared and Jed? Sure, maybe we can file under 2.0 gaia nice-to-haves, since it's not hurting anything, and we haven't cleared the 2.0 blockers yet?
Flags: needinfo?(6a68)
I followed Jared's suggestion re parent bug. I would still like to delete the code from (or at least hide the UI in) the Test FxA app, so that the latter is a faithful representation of what we are trying to do.
Blocks: 996054
No longer blocks: 989363
That sounds good to me. Remove the test and replace it with a comment pointing to the new bug?
Flags: needinfo?(jparsons)
Summary: [FxAccounts] 'user is already signed in' message shows when undergoing forced authentication → [FxAccounts] Move refreshAuthentication test from IAC-API TestFXA app to RP-API UITest app
No longer blocks: 996054
Experimenting with a project whiteboard tag, "[fxa4fxos2.0]". Feedback welcome.
Whiteboard: [fxa4fxos2.0]
Priority: -- → P3
Assignee: spenrose → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.