Adding prompt message on UserManager when force-sign-in is enabled. |
||||
Issue descriptionAdding prompt message on UserManager when force-sign-in is enabled.
,
Aug 28 2017
Could you please mention that the local administrator requires login? Maybe something along the lines of: "Your local administrator has configured Chrome to require sign-in [with an account that matches: <RestrictSigninToPattern>]." The part in square brackets should only be shown when RestrictSigninToPattern is set. Please keep in mind that the text should also work during first run -- "please unlock your profile" doesn't make sense there since (from the perspective of the user) there is no profile yet that could be unlocked.
,
Aug 28 2017
,
Aug 28 2017
The value of RestrictSigninToPattern is a regular expression. Display the value will confuse the user for sure. That's why I only says 'corporate'. And later, I could provide another policy so that admin is able to change this msg if necessary. Force-sign-in policy is designed for deploying profile policy. It doesn't make sense if admins want user sign in with their gmail account because they can't setup cloud policy for personal profile. Also, there is always a profile during first run. A default profile will be created (and locked with force-sign-in policy enabled) automatically if there is no profile. I could add 'You local administrator has configured Chrome'. I didn't say that only because I want to keep the message as short as possible. Do you think it's important to mention 'administrator ' in the msg?
,
Aug 29 2017
> The value of RestrictSigninToPattern is a regular expression. Are you sure it's a regular expression? The docs [1] say so, but the example that is given looks more like a glob pattern: "*@domain.com". Depending on what is correct, could you please fix either the text or the example? > Also, there is always a profile during first run. A default profile will be created (and locked with force-sign-in policy enabled) automatically if there is no profile. I've seen that. Technically, there is a profile. But not from the perspective of the user. "Please unlock your profile" is confusing since the user is not aware that they have a profile already. > I could add 'You local administrator has configured Chrome'. I didn't say that only because I want to keep the message as short as possible. Do you think it's important to mention 'administrator ' in the msg? Yes, it is important to mention the local administrator because otherwise the user could think that Chrome is enforcing sign-in. This would go against the principle of transparency. [1] http://www.chromium.org/administrators/policy-list-3#RestrictSigninToPattern
,
Aug 29 2017
Yes, it's a regular expression. And there is also a hack so that *@domain.com also works. https://cs.chromium.org/chromium/src/components/signin/core/browser/signin_manager.cc?sq=package:chromium&dr=CSs&l=293 Ok, I think we should just avoid mention 'Profile' and I'll mention administrator.
,
Aug 29 2017
I put you as reviewer of new text: https://chromium-review.googlesource.com/c/chromium/src/+/641857
,
Aug 31 2017
Still I think it would be very nice if the message could mention the pattern that the email address needs to follow. It would seem easy to create a special case for patterns whose only wildcard is a .* (or just a *) at the start - this should be the majority. Thus I'd suggest: if pattern starts with .*@ or *@ and has no other regexp special characters: "Your administrator requires you to sign into Chrome with your @<domain> account." else "Your administrator requires you to sign into Chrome with an account that matches the following pattern: <pattern>."
,
Sep 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/da0bec28176100b7c15adb7ce875e97cdf308a16 commit da0bec28176100b7c15adb7ce875e97cdf308a16 Author: Thiemo Nagel <tnagel@chromium.org> Date: Mon Sep 04 11:13:34 2017 Fix RestrictSigninToPattern documentation The pattern is documented as regular expression, thus the example should also be a regular expresson. Bug: 759197 Change-Id: I9267dd3dabc5e397f23890e30cf263f396b04a4d Reviewed-on: https://chromium-review.googlesource.com/645637 Reviewed-by: Owen Min <zmin@chromium.org> Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Thiemo Nagel <tnagel@chromium.org> Cr-Commit-Position: refs/heads/master@{#499478} [modify] https://crrev.com/da0bec28176100b7c15adb7ce875e97cdf308a16/components/policy/resources/policy_templates.json
,
Oct 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f13ab2c3cb1c3f206a47b349daee64ff95f58590 commit f13ab2c3cb1c3f206a47b349daee64ff95f58590 Author: Owen Min <zmin@chromium.org> Date: Tue Oct 10 22:15:28 2017 Improve the words of force-sign-in prompt message. Bug: 759197 Change-Id: Ibdaea7ca726a6fa3f3b845a43502de551540802c Reviewed-on: https://chromium-review.googlesource.com/641857 Reviewed-by: Owen Min <zmin@chromium.org> Reviewed-by: Georges Khalil <georgesak@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#507791} [modify] https://crrev.com/f13ab2c3cb1c3f206a47b349daee64ff95f58590/chrome/app/generated_resources.grd
,
Nov 7 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Aug 25 2017