Closed Bug 982798 Opened 10 years ago Closed 10 years ago

authentication error after changing my password and signing in again

Categories

(Cloud Services :: Server: Firefox Accounts, defect)

Product:
Cloud Services
Component:
Server: Firefox Accounts
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Gavin, Unassigned)

References

Details

(Whiteboard: [qa+]) 

My STR were roughly:
1) Sign in to Firefox
2) Go to https://accounts.firefox.com/settings, change my password
3) Restart Firefox
4) Get "need to sign in again" error state UI
5) Sign in again with new password

The sign in succeeds, but Firefox then quickly encounters another authentication error, kicking me back into the "sign in again" UI:

FXA UI Observer: fxaccounts:onlogin
FXA UI Observer: fxaccounts:onverified
1394652955994	Sync.BrowserIDManager	ERROR	Authentication error in _fetchTokenForUser: AuthenticationError(TokenServerClientServerError({"now":"2014-03-12T19:35:55.965Z","message":"Authentication failed.","cause":"invalid-client-state","response_body":"{\"status\": \"invalid-client-state\", \"errors\": [{\"location\": \"body\", \"name\": \"\", \"description\": \"Unauthorized\"}]}","response_headers":{"content-type":"application/json; charset=UTF-8","date":"Wed, 12 Mar 2014 19:35:56 GMT","server":"nginx/1.4.4","x-timestamp":"1394652956","content-length":"111","connection":"keep-alive"},"response_status":401}))
FXA UI Observer: weave:service:login:error
1394652956018	Sync.BrowserIDManager	ERROR	Background fetch for key bundle failed: AuthenticationError(TokenServerClientServerError({"now":"2014-03-12T19:35:55.965Z","message":"Authentication failed.","cause":"invalid-client-state","response_body":"{\"status\": \"invalid-client-state\", \"errors\": [{\"location\": \"body\", \"name\": \"\", \"description\": \"Unauthorized\"}]}","response_headers":{"content-type":"application/json; charset=UTF-8","date":"Wed, 12 Mar 2014 19:35:56 GMT","server":"nginx/1.4.4","x-timestamp":"1394652956","content-length":"111","connection":"keep-alive"},"response_status":401}))

The account I'm testing with is synctest@gavinsharp.com.
I sent ckarlof and rkelly some token server request information.
I requested the server DB contents for this account in Bug 982925.

I suspect somehow you got a corrupted x-client-state interleaved with the value one associated with your password, which would cause repeated "invalid x-client-state" errors. Reseting your password should clear this problem (and I believe did).

If we ever calculated the x-client-state based on an empty kB, that would be bad.
I switched to using ffsyncer@gavinsharp.com (a recently created account, rather than the ancient synctest@gavinsharp.com), and still see the same errors. Sent some X-Client-State info to ckarlof/rkelly/others via email.
Whiteboard: [qa+]
Depends on: 982925
Sounds like this is being tentatively addressed by https://github.com/mozilla/fxa-js-client/pull/97/files.
this should be fixed on train 6
Train 6 was deployed and this should be fixed: Bug 983833.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.