New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 850925 link

Starred by 3 users
Status: Duplicate
Merged: issue 877424
Owner:
steve...@chromium.org
Closed: Sep 20
Cc:
vkasatkin@google.com
█ rtillilie@chromium.org
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Managed network settings configurable by users

Project Member Reported by vnikolov@chromium.org, Jun 8 2018 
Chrome Version: 66,67,68
Chrome OS Version: 66,67,68
Chrome OS Platform: Tested on Pixelbook
Network info: WPA/WPA2 Enterprise (802.1x) 
example: PEAP, mschapv2
Do not check for certificate authority


Steps To Reproduce:
(1) Add a network in the Admin Console (both user and device based)
(2) Specify "Extensible Authentication Protocol", "Inner Protocol" and "Server Certificate Authority"


Expected Result:
Network should appear in the list with all the settings managed by admin (User shouldn't be able to change them)

Actual Result:
Networks appears, however both "Extensible Authentication Protocol" and "Inner Protocol" are changeable from the drop down menus. "Server Certificate Authority" is reverted to "default"

In the policy list the open network configuration appears fine (e.g \"UseSystemCAs\": false\)

How frequently does this problem reproduce? Each time I tried

Logs (from test account and device PII protected):
https://drive.google.com/open?id=1UBVjbrziW94iG2Gyc9-MwBle6-20PLfe

Comment 1 by vkasatkin@google.com, Jun 8 2018

Cc: vkasatkin@google.com jayhlee@chromium.org
Components: Enterprise
Labels: Hotlist-Enterprise M-67 M-68

Comment 2 Deleted

Comment 3 by jingwee@chromium.org, Jun 12 2018

Status: Untriaged (was: Unconfirmed)

Comment 4 by igorcov@chromium.org, Jun 18 2018

Owner: atwilson@chromium.org
For Drew to find somebody to work on this.

Comment 5 by atwilson@chromium.org, Jun 19 2018

Owner: steve...@chromium.org
Steven, does your team own that UI?

Comment 6 by steve...@chromium.org, Jun 19 2018

Labels: -Pri-3 -M-67 -M-68 Pri-2
Status: Assigned (was: Untriaged)
It sounds like this is just a UI bug? In which case, yes, this is for the UI team.

The new configuration UI goes through ONC validation (yay!) so we should make sure that changes to these properties from the config UI do not actually stick.

If the changes are allowed, it may be that the generated policy is only recommending these settings, not enforcing them.

There is an open bug that we don't correctly show indicators for recommended settings.

Comment 7 by hendrich@chromium.org, Sep 20

Mergedinto: 877424
Status: Duplicate (was: Assigned)
This is just a UI bug, so any changes the user makes in the UI won't be applied.
We already have someone working on this to correctly enable/disable input fields and show policy indicators.
►

Sign in to add a comment