Issue metadata
Sign in to add a comment
|
ForceBrowserSignIn policy is not working as expected |
||||||||||||||||||||||
Issue descriptionChrome Version: (#71.0.3559.6) OS: (Mac_OS) What steps will reproduce the problem? (1) Enable ForceBrowserSignIn policy (2) Launch Chrome and sign into chrome browser What is the expected result? Able to successfully log into chrome browser. What happens instead? Not able to sign into chrome browser With reference to Issue 887381, assigning it to jam@
,
Sep 28
+zmin in cc
,
Sep 28
What are the steps to bring up that settings editor on Mac? I tried on Windows canary and can't reproduce this.
,
Oct 1
[bulk edit] - This issue is marked as a stable blocker for M70. We are two weeks away from M70 Stable. Please take a look urgently!
,
Oct 1
Hi, I can't repo this on Mac either. I have tried both Chrome with and without network-service flag. I have also tested it with both Canary(71.0.3567.0) and Beta(70.0.3538.35).
,
Oct 1
Also testing policy on Mac requires ProfileManager which is complicated to setup. Here is a short hacky way to enable policy. https://goto.google.com/gznvf (Internal Link)
,
Oct 2
I checked the commit history. The patch is landed in 71.0.3561.0 while this issue is reported based on 71.0.3559.6. I think this issue has been fixed already. https://chromiumdash.appspot.com/commits?commit=c02342fb25472c49e9c251635778227a4ad1814e&platform=Mac
,
Oct 2
Close the issue as duplicate. Feel free to reopen it if the issue still exist. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kkaluri@chromium.org
, Sep 28