Update policy documentation for sign-in pattern policies |
|||||
Issue descriptionDICE blurred a bit the lines about what signing in to Chrome means. We need to update the documentation RestrictSigninToPattern (and other sign-in related policies) and for ForceBrowserSignin to make it clear to admins that these policies refer to the Chrome primary account.
,
Sep 28
Let's make sure as part of this documentation update to explain what happens when both ForceBrowserSignin and AllowBrowserSignin are set.
,
Sep 28
,
Oct 8
,
Oct 9
The bulk of this bug was already implemented on Issue 890396. The only remaining work on this bug is to update the description for RestrictSigninToPattern as instructed in https://docs.google.com/document/d/1CVKpcbKVZ6J1kLHWw9I_KjJhk3Yqa8DFW8ZSF76vgXs/edit?usp=sharing
,
Oct 10
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4fe9842151c54039ede374aef75121a61051b479 commit 4fe9842151c54039ede374aef75121a61051b479 Author: Mihai Sardarescu <msarda@chromium.org> Date: Wed Oct 10 16:03:37 2018 Update caption and description for policy RestrictSigninToPattern. This change is necessary to make it clear that RestrictSigninToPattern only refers to the browser primary account. Bug: 889838 Change-Id: I5eecf72dd69658c3701bf5e99c5fbbc7194fec2a Reviewed-on: https://chromium-review.googlesource.com/c/1269871 Reviewed-by: Drew Wilson <atwilson@chromium.org> Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#598351} [modify] https://crrev.com/4fe9842151c54039ede374aef75121a61051b479/components/policy/resources/policy_templates.json
,
Oct 10
Should we mark this as Fixed, Mihai?
,
Oct 10
Yep, that was the last thing we thought was needed. I personally think that in the long run it would be good to rename the policies (or at least deprecate the old one and replace it with a new one that is correctly named to avoid confusion). But I followed the suggestion from enterprise folks and only updated the documentation now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by msarda@chromium.org
, Sep 27