[signin] Investigate revocation of old tokens |
|||||||
Issue descriptionChrome recently started revoking the old token when receiving a newer one. A recent report ( bug 772122 ) may suggest that the old token may still be in use somehow, and causing authentication errors. It is not clear how this could happen, but it deserves some investigation to avoid a potential regression.
,
Nov 15 2017
Please add affected OSs.
,
Nov 16 2017
,
Nov 17 2017
Did some investigation and tried to repro the bug, but found nothing. Removing the blocking stable label, but keeping the bug open in case we have more ideas how to investigate.
,
Dec 18 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 18 2017
Keeping assigned as this may be important. May close in a month if it turns out this is not an issue.
,
Jan 18 2018
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 19 2018
The issue we have seen were all related to token encrypt problems. There are no known issues related to the revoking the tokens. I am closing this bug. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by msarda@chromium.org
, Nov 15 2017