Open Bug 1737383 Opened 3 years ago Updated 2 years ago

In-browser "Manage Accounts" links may show a different account than your Sync account

Categories

(Firefox :: Firefox Accounts, defect)

defect

Tracking

()

Tracking Status
firefox95 --- affected

People

(Reporter: dveditz, Unassigned)

References

(Depends on 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #1421164 +++

I'm in the same situation as Mark in bug 1421164:

For annoying reasons, I'm forced to use a different email address for AMO vs Sync. If I type accounts.firefox.com into the urlbar, I see my AMO account which surprised me - it took me a while to realize why the device list showed no devices.

However, unlike bug 1421164 where Ryan said

all in-product elements which open the page do the right thing via query strings and/or other magic

I'm relieved to hear this part :-)

The in-product links do NOT do the right thing for me. Did the parameters used on the server change somewhere in the last 4 years? It looks like it's trying to do the right thing: there's an email parameter which gives my sync email, and a uid parameter that I assume matches. But if I have previously logged into SUMO or AMO with my other account then that's the one I get on the accounts.firefox.com page.

I've repeated this result from the "Manage Accounts" links from

  • My FxA avatar on the toolbar
  • the Firefox Account submenu under the hamburger button
  • the link from about:preferences#sync
Flags: needinfo?(markh)

Yes, I can reproduce this. Using "manage account", I see the URL https://accounts.firefox.com/settings?context=fx_desktop_v3&entrypoint=fxa_discoverability_native&uid=<snip>&email=<snip personal email> (ie, my sync account) but the page is actually showing my AMO account.

Vijay, can you help here?

Flags: needinfo?(markh) → needinfo?(vbudhram)
Summary: Manually visiting accounts.firefox.com may show your AMO account rather than your Sync account → In-browser "Manage Accounts" links may show a different account than your Sync account

Hey Daniel/Mark,

I just tested this and can verify the behavior you describe. Last year we moved our settings page from BackboneJS to React and I suspect that this bug was introduced with that. I've created https://github.com/mozilla/fxa/issues/10824 that we will triage.

Flags: needinfo?(vbudhram)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.