I'm spinning this out from Bug 1112962 Comment 6, as I'm fairly sure we've got two separate bugs on our hands. User :Rolcol reports that sync has started showing the "Incorrect account name or password" error bar in the last few days, despite not changing/resetting password for at least a month. Disconnecting+reconnecting sync fixes the issue. But this behaviour seems to be gradually propagating around all the clients in the sync cluster. Client debug logs show an "invalid-client-state" error when talking to the tokenserver. :Rolcol if you could attach client logs to this new bug that would be great. Inspecting the client-side password databases and comparing between working and non-working clients, we see that: * working clients all have FxA credentials with matching values for kB * non-working client has FxA credentials with a different value for kB, and an extra "unwrapBKey" entry * non-working client reports that the FxA credentials were Last used: Sep 24, 2014 5:28PM MST, Last Changed: Dec 18, 2014 * the last-changed date corresponds to when the errors started occurring, but does not correspond to any password change events on the account Inspecting the server-side synced password data, we see a single entry with {"deleted": true}. The user does not use firefox's password manager to store site passwords. I wonder if this entry corresponds to a (deleted) version of the FxA credentials.

These are the same logs attached to Bug 1112962 Comment 8

While I do not allow Firefox to remember my passwords, there was one occasion where a new sync client was connected before I disabled the "Remember passwords for sites" feature. I deleted this saved password when I was instructed to inspect the kB value.

(In reply to Rolcol from comment #2) > While I do not allow Firefox to remember my passwords, there was one > occasion where a new sync client was connected before I disabled the > "Remember passwords for sites" feature. I deleted this saved password when > I was instructed to inspect the kB value. FTR, deleting the "firefox accounts" saved password will certainly cause Sync to require a reauthentication and will re-save the entry in the password manager. Note also that this re-save happens even if you have elected to not save passwords (ie, it is expected that the FxA entry will re-appear even with this option disabled) - and note also that this entry does *not* contain your password.

This three-year-old bug seems likely to no longer be valid, but putting it in the right component for future triage.

Yeah, this is no longer actionable as things stand. RolCol, please reopen this bug if you are still having problems around sync (which would mean you have extraordinary patience after 3 years!)