New issue
Advanced search Search tips

Issue 763292 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Sep 2017
Cc:
pastarmovj@chromium.org
ajha@chromium.org
zmin@chromium.org
nyerramilli@chromium.org
ligim...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Forced SignIn policy is not working as expected

Project Member Reported by kkaluri@chromium.org, Sep 8 2017 
Chrome Version: 61.0.3163.79
OS: (Win2K12-Server, Win10-Client)

What steps will reproduce the problem?
(1) Enable "Force Sign in for Google Chrome" policy in server.
(2) Update group policy in client using "gpupdate /force"
(3) Launch google chrome in client machine.

What is the expected result?
Chrome should ask for browser sign in before launching chrome.

What happens instead?
Chrome launching startup pages without asking for browser sign in.

Attaching the Screen-Cast for reference.
Force-SignIn.mp4
2.3 MB View Download

Comment 1 by ligim...@chromium.org, Sep 8 2017

Labels: Needs-Feedback
The feature is targeted for M62 as per the launch bug:  Issue 751230. Can you please try in latest dev and update.

Lopping to zmin@ who is the feature owner.

Comment 2 by emaxx@chromium.org, Sep 11 2017

Cc: zmin@chromium.org
Mergedinto: 751230
Status: Duplicate (was: Unconfirmed)
Closing this, as the feature will be launched only in M62, as per comment 1.

The policy templates should have been updated to not include this policy for M61 (see  bug 760296 ), but apparently that hasn't happened. According to some internal discussions, most likely the fixed templates will be published with the next update of Chrome Stable.
►

Sign in to add a comment