New issue
Advanced search Search tips

Issue 888335 link

Starred by 2 users
Status: Duplicate
Merged: issue 889366
Owner: ----
Closed: Oct 9
Cc:
droger@chromium.org
ew...@chromium.org
bsazonov@chromium.org
sabineb@chromium.org
viswa.karala@chromium.org
msarda@chromium.org
tangltom@chromium.org
jlebel@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

account-consistency causes issue if two accounts are logged in

Reported by tldr@fernandomiguel.net, Sep 23 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.22 Safari/537.36

Steps to reproduce the problem:
1. login and enable chrome to one google account
2. login to Gsuite with a different account (this is the primary account of this chrome profile)

What is the expected behavior?
on start, for GSuite account to login into all the previously open tabs

What went wrong?
tabs try to login into the browser account instead of the GSuite account

Did this work before? Yes M69

Chrome version: 70.0.3538.22  Channel: n/a
OS Version: OS X 10.14.0
Flash Version: 

till M70 and #account-consistency set to old behaviour, browser would restore just fine and login into the correct session, not mixing Browser Sync account and google session cookie

now that the Browser shares the session, it is trying to login restored tabs to the wrong account.

not only is this a security risk as data could be leaked, but requires the user to be re-logging all tabs to the right account.

Comment 1 by vamshi.kommuri@chromium.org, Sep 23

Labels: Needs-Bisect Needs-Triage-M70

Comment 2 by treib@chromium.org, Sep 24

Cc: msarda@chromium.org
Components: -Services>Sync Services>SignIn
Labels: -Needs-Bisect
I believe this is working as intended: On restarting Chrome, Chrome will try to reorder the signin cookie accounts so that the signed-in-to-Chrome/Sync account is the first one.
Over to signin folks who can probably explain this better than me.

Comment 3 by viswa.karala@chromium.org, Sep 24

Cc: viswa.karala@chromium.org
Labels: Triaged-ET Proj-MacMojave
Thanks for filling the issue...

As per comment# 0 it seems that the issue is specific to Mac Mojave(10.14.0). As we don't have that particular OS-Mac to test and confirm the issue from TE end. Hence adding Proj-MacMojave label to it.

Thanks...!

Comment 4 by tldr@fernandomiguel.net, Sep 24 

@viswa you saying the version of MacOS affects how Chrome sorts the cookie jar?

Comment 5 by rsesek@chromium.org, Sep 24

Labels: -Proj-MacMojave
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 9

Cc: droger@chromium.org bsazonov@chromium.org tangltom@chromium.org ew...@chromium.org sabineb@chromium.org jlebel@chromium.org
Status: WontFix (was: Unconfirmed)
--Chrome Identity automated triaging--

This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. 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

Comment 7 by ew...@chromium.org, Oct 9

Mergedinto: 889366
Status: Duplicate (was: WontFix)
This is a duplicate of another issue asking for the ability to have a specific ordering of the cookies.
►

Sign in to add a comment