Make auth failure during device registration drive FxA to "separated". #5756
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5755. Sorry, I don't have my build environment set up in order to test this, but I figured I'd at least put up a draft PR to communicate the intent of that issue.
Previously, an auth failure during device registration would drive the
FxA state machine to "doghouse", which is a special terminal state for
when the FxA server tells the client that it needs to upgrade itself
before it can continue using the FxA APIs.
The appropriate state for auth failures is "separated", which prompts
the user to re-enter their password to reconnect to the account.