Enable add in profile manager (want to disable) through Local Group Policy Editor
Reported by
weaver.j...@gmail.com,
Apr 3 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Open Local Group Policy Editor (gpedit.msc) 2. Set the Enable add in profile manager to Disabled 3. Launch Google Chrome to check What is the expected behavior? Google Chrome is not supposed to allow more users to be added. What went wrong? I set the policy listed above through GPO to disable and it still let me add another person using profile manager. Did this work before? N/A Chrome version: 57.0.2987.133 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: 25.0.0.127
,
Apr 4 2017
Untriaging it so that it gets addressed.
,
Apr 7 2017
Assigning to George since it's a Windows issue.
,
Apr 11 2017
Assigning to zmin.
,
Apr 11 2017
Hi weaver.jarod0312, Thanks a lot for the reporting. When you say "profile manager", do you manage the profils on the chrome settings page(chrome://setting) which contains many other stuff like sign in, setup home page, setup theme, etc? If this is not your case, please tell me, otherwise: This is actually by design. The policy is introduced since M39 and can only be used to disable adding new profile on UserManager. FYI, to open UserManager, you can click your profile icon on the top-right corner then click "Manage People". You shouldn't see the 'Add Person' button on UserManager if the policy(Enable add person in profile manager) is disabled. If you do, please tell me. I agree that a policy only disables adding profile in one place but not the other doesn't make any sense. However, the reason is this policy is actually a legacy of an abandoned project. In that project, adding profile on UserManager and on chrome settings page are completely two different things. Very luckily, current chrome setting page is going to be deprecated soon and there is no more profile managing options on the new one. UserManager become the only place that user can add new profile after the deprecation. In the other word, this policy will makes sense again automatically. You'll see the new settings page in the upcoming version. If you're interested, you can check it by go chrome://md-settings In the end, I think the descriptions of the policy is confused as it uses both "profile manager" and "user manager". If you can confirm my assumption above, I will improve the descriptions for sure. Regards, Owen
,
Apr 12 2017
That's correct. I meant the chrome://settings page.
,
Apr 12 2017
+ewald https://www.chromium.org/administrators/policy-list-3#BrowserAddPersonEnabled The description of the policy above uses both 'profile manager' and 'user manager' at the same time. I think we shall just use 'user manager' for consistency. Any suggestions?
,
Apr 12 2017
Moving all references over to "user manager" SGTM.
,
Apr 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bbafd853034a965c4ffb62803bb002c091211fd0 commit bbafd853034a965c4ffb62803bb002c091211fd0 Author: zmin <zmin@chromium.org> Date: Thu Apr 13 15:34:00 2017 Change the description of BrowserAddPersonEnabled policy. Replacing 'profile manager' with 'user manager' for consistency. BUG= 707828 Review-Url: https://codereview.chromium.org/2815133002 Cr-Commit-Position: refs/heads/master@{#464417} [modify] https://crrev.com/bbafd853034a965c4ffb62803bb002c091211fd0/components/policy/resources/policy_templates.json
,
Apr 20 2017
ADMX/ADM files have been updated in 59.0.3071.9. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ligim...@chromium.org
, Apr 3 2017