New issue
Advanced search Search tips

Issue 851454 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 17
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

FR: Allow sign in to local profile following ForcedBrowserSignin

Reported by peter.ar...@telegraph.co.uk, Jun 11 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36

Steps to reproduce the problem:
1. Have a local Chrome profile setup
2. Rollout the ForcedBrowserSignin Chrome policy
3. See the local profile now locked (by design)
4. Be forced to create a new 'online' profile, signed into a Google account
5. Local Chrome profile is in limbo

What is the expected behavior?
Be able to login to a Google account at step 3., linking that local data to a Google account

What went wrong?
The profile is locked, meaning you need to start delving into system files to pick out bookmarks, cookies etc. to carry over to the newly created profile folder

Did this work before? No 

Chrome version: 66.0.3359.170  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

It would make more sense to at least have a flag/setting in the ForceBrowserSignin policy to allow/force users to sign into this local profile instead of locking it.
Current behaviour makes rolling this out ~2000 users very difficult.
 
Components: Enterprise
Owner: privard@chromium.org
Status: Assigned (was: Unconfirmed)
this is by design. give to PM privard@ to resolve.

Understood this is by design, as referenced here: https://bugs.chromium.org/p/chromium/issues/detail?id=175880#c185

That said, will there be absolutely no review/revisit of this behaviour? As mentioned, it's making deployment at enterprise level difficult.
Status: WontFix (was: Assigned)
We announced a new Chrome Browser management feature at Next 2018 that allows administrators to set policies from the Google Admin console, and these apply across all active browser profiles. The managed users do not need Google accounts, nor do they need to be signed in to the browser.

There are more details on this feature at:
http://g.co/chromecloudmanagement

Marking this as WontFix as we currently don't have plans to offer this functionality via ForcedBrowserSignin, but similar functionality will soon be available via Chrome Browser Cloud Management.

Sign in to add a comment