New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 814148 link

Starred by 1 user

Issue metadata

Status: Available
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

AccountReconcilor optimizations after cookie/token binding

Project Member Reported by droger@chromium.org, Feb 21 2018

Issue description

If we reach a point where all Gaia cookies are bound to the LST in Chrome, then a lot of work currently done by the AccountReconcilor becomes unnecessary.

This is because cookies are automatically invalidated on the server when the token becomes invalid. When this happens, the account remains visible on the web, but a reauth is triggered when it is selected.

In many (all?) cases, it would be better for the AccountReconcilor to do nothing, because the default experience when a cookie is invalidated on the server is better than completely removing the cookie from Chrome (which is the current reconcilor behavior).

To do this, we need to check that:
- all new cookies are bound to the tokens in all scenarios
- all cookies that were issued before cookie-token binding was implemented are now invalid (might require waiting for genuine expiration of these cookies, which can be very long)

 

Comment 1 by droger@chromium.org, Feb 21 2018

Cc: msarda@chromium.org

Comment 2 by yananj@google.com, Feb 22 2018

Cc: yananj@google.com
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 26 2018

Status: Available (was: Assigned)
--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
Status: Assigned (was: Available)
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 3

Status: Available (was: Assigned)
--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

Sign in to add a comment