Handle missing DMServer entry through re-registration
This CL handles the scenario of DMServer reporting a 410 status code
(missing/unknown/purged client ID) by trying background
re-registration. If this fails, the user is marked as requiring an
online sign-in.
DD: go/handle-purged-user-sessions
Bug: 870616
Change-Id: I4a4c2370c36f5464752029d755d23221cd064b0e
Reviewed-on: https://chromium-review.googlesource.com/c/1227939
Commit-Queue: Alexander Hendrich <hendrich@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#600359}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 3a845098f5f445e54eef1f66581377f7a8a708064 files changed
