Closed Bug 1887739 Opened 2 years ago Closed 1 year ago

Reconecting an account using the oauth flows fails.

Categories

(Firefox :: Firefox Accounts, defect, P3)

defect

Tracking

()

RESOLVED FIXED
128 Branch
Tracking Status
firefox128 --- fixed

People

(Reporter: markh, Assigned: teshaq)

References

Details

(Whiteboard: [fxsync-])

Attachments

(1 file)

We fail to reconnect an account due to an external password change. The problem seems to be that we assume the account already has a session token from when the account initially logged in - however, we discarded that when the account because disconnected. Specifically, in the reconnect case, we fail to get a session token here.

The console reports:

1711392918796   FirefoxAccounts ERROR   Failed to handle FxAccountsWebChannel message: Error: INVALID_STATE(resource://gre/modules/FxAccountsOAuth.sys.mjs:189:13) JS Stack trace: completeOAuthFlow@FxAccountsOAuth.sys.mjs:189:13
completeOAuthFlow@FxAccounts.sys.mjs:886:23
oauthLogin@FxAccountsWebChannel.sys.mjs:515:40
async*_receiveMessage@FxAccountsWebChannel.sys.mjs:239:12
listener@FxAccountsWebChannel.sys.mjs:387:16
deliver@WebChannel.sys.mjs:258:14
tryToDeliver@WebChannel.sys.mjs:67:17
receiveMessage@WebChannelParent.sys.mjs:39:50
...

(setting severity to S4 as this capability is behind a pref. Is there a tracking bug this should block?)

Assignee: nobody → teshaq
Status: NEW → ASSIGNED
Whiteboard: [fxsync-]
Pushed by teshaq@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bf8c8fac055d Removes force_auth fxa path and uses connect path instead.r=markh,settings-reviewers
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: