Fail to sign in to an existing account with "Cannot create account"/"You must meet certain age requirements to create a Mozilla account."
Categories
(Cloud Services :: Server: Firefox Accounts, task)
Tracking
(Not tracked)
People
(Reporter: markh, Unassigned)
Details
I've an existing (test) account which I've successfully used to sign in to one desktop profile.
On another desktop profile, I restart the profile and whenever I try and sign in to that account, I get redirected to https://accounts.firefox.com/cannot_create_account.
So I guess there are 2 problems here:
-
There's a regression in that previously if your browser thought you were too young, a restart would solve that. But now, if a user accidentally "fat-fingers" an incorrect age, they appear stuck forever. (It may be that I need to remove all local storage or similar for the accounts domain, but a regular user would be effectively and permanently stuck.
-
I'm not actually trying to create an account - I'm trying to log in to an existing account. The error makes no sense in this context.
|
Reporter | |
Comment 1•2 years ago
|
||
(yeah, clearing site data for a.f.c did indeed resolve the issue)
|
||
Comment 2•2 years ago
|
||
Are you sure you closed your browser all the way? I just tried:
- Try to register at accounts.firefox.com
- Type age as 9
- get blocked
- Close browser, open again
- No longer blocked at accounts.firefox.com
Lauren also looked at the code and said it's cookie only and hasn't changed for a while
|
|
Reporter | |
Comment 3•2 years ago
|
||
Lauren also looked at the code and said it's cookie only
Wouldn't that explain my STR though? Assuming I don't have Firefox set to clear all cookies on exit, and this being a first-party cookie, I'm not surprised to find it survives a restart? If it's a session cookie I think the problem might be restoring the session also restores those cookies.
and hasn't changed for a while
Fair enough - I just seem to recall it not working the way I experienced it. I guess it is possible it always worked that way with session restore, so I'll just kill this - thanks!
Description
•