"Server CA certificate" is showing as "Default" when configured as 'Do not check" in policy |
|||||||||
Issue descriptionChromeOS version: starting material design, 66 ChromeOS device model: any Case#: 16734646 Description: "Server CA certificate" is showing as "Default" when configured as 'Do not check" in policy Steps to reproduce: 1. Configure WPA2 Enterpsie network, set "Do not check" in Server Certificate Authority, do not fill username and password, like in "admin.png" 2. Update the policy, try to connect to network. Current Behavior / Reproduction: Observe "Server CA certificate" as "Default" on 66+ version OS (with material design UI). Policy still shows "UserSystemCAs": false And we received report that some customers cannot connect to network, unless they manually select "Server CA Certificate" as "Do not check". Expected Behavior: "Server CA Certificate" is shown as "Do not check", as in per-material design UI (Screenshot.png)
,
Sep 3
Hi all, I filed a similar report for this - https://bugs.chromium.org/p/chromium/issues/detail?id=850925 I'm not sure if some work was done in the other crbug. Thanks!
,
Sep 6
I'm not sure if this is a problem with the new UI (which has been around for multiple releases now), or the more recent cert related changes. I'll try to take a look to see if it's a UI thing.
,
Sep 10
This is in fact a bug in the new UI, just one that nobody noticed until recently.
,
Sep 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3d985b20dc24dd492da9473ea2a0ee050612431c commit 3d985b20dc24dd492da9473ea2a0ee050612431c Author: Steven Bennetts <stevenjb@chromium.org> Date: Wed Sep 12 19:34:32 2018 Network config: Set server CA to do-not-check correctly Bug: 879779 Change-Id: I58bb5a4ad5498b394ca06699b5741c285f5188b4 Reviewed-on: https://chromium-review.googlesource.com/1217847 Reviewed-by: Alexander Hendrich <hendrich@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#590788} [modify] https://crrev.com/3d985b20dc24dd492da9473ea2a0ee050612431c/ui/webui/resources/cr_components/chromeos/network/network_config.js
,
Sep 12
,
Sep 12
This is actually a very simple fix that would be nice to have in M-70; merge requested.
,
Sep 13
Approved for M70
,
Sep 13
,
Sep 13
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/77d62031482c84ef39093425aaacf616b3cdc8ba commit 77d62031482c84ef39093425aaacf616b3cdc8ba Author: Steven Bennetts <stevenjb@chromium.org> Date: Thu Sep 13 17:49:49 2018 Network config: Set server CA to do-not-check correctly TBR=stevenjb@chromium.org (cherry picked from commit 3d985b20dc24dd492da9473ea2a0ee050612431c) Bug: 879779 Change-Id: I58bb5a4ad5498b394ca06699b5741c285f5188b4 Reviewed-on: https://chromium-review.googlesource.com/1217847 Reviewed-by: Alexander Hendrich <hendrich@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#590788} Reviewed-on: https://chromium-review.googlesource.com/1224601 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#372} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} [modify] https://crrev.com/77d62031482c84ef39093425aaacf616b3cdc8ba/ui/webui/resources/cr_components/chromeos/network/network_config.js
,
Jan 14
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by marchuk@chromium.org
, Aug 31