Hi all,

Just to add, as we have another report of this behavior, that intermittently the managed network pushed to Devices, doesn't appear at all in the Known networks list, although it is visible in Chrome://policy.

Thanks!

Behavior seems to be different from "user" level WiFi networks and forgotten network won't reappear anymore.

[Krishna: Can you triage this for us please]

As verified in M60.0.3112.101:9592.82.0	stable yuna, the device-level managed work could be "forgetten". After that, the device remained unconnected to the network. The "forgotten" network did appear in the available network list but without the Enterprise icon. It could be connected and was working normally like an unmanaged network and the configurations could be modified.  Only after a reboot, the network settings were restored according to the device-level policy.

Also verified in M61.0.3163.41:9765.23.0 dev caroline seeing the same results.

This could become an issue in EDU. Adding RBS to raise visibility.
- Assigning to Drew to request help in narrowing the root cause.

If this is a regression and an M-60 stable blocker, can we get QA support to do a bisect? Once we've narrowed down the candidate CLs that regressed this, Pavol can help locate the owner.

Can we also verify if this a new issue with M60? (e.g. not there with M59)

+tbarzic
I'm OOO until Tuesday EOD, but could this be related to changes for bug 705024 or bug 700131?
If I'm reading CL https://codereview.chromium.org/2754903002 correctly, being able to remove a network set through device policy ONC through the networkingPrivate API seems to be intended behavior there.

Not sure if the network config UI goes through that API though.
 Thanks,
Pavol

Can we find out why this is intended ?
- I'm trying to understand the use case.

I tried 59.0.3071.135:9460.76.0 stable yuna, M59.0.3071.47:9460.34.0 beta yuna and even much older M59.0.3064.0:9438.0.0 dev yuna have the behavior is the same as #6 - able to forget the network and the network does show in list without the Enterprise icon.

no, it's not intended :/

though, the issue was not introduced by https://codereview.chromium.org/2754903002 - it was there before, it's just that the cl in question apparently did not completely handle the use case

(what changed is that Forget button used to be disabled in the options UI, so the issue was not hit)


(note: I'm ooo so I I might not reply in timely manner)

M58.0.3029.145:9334.74.0 stable yuna does not have the issue with old UI. There is no "forget" option and the managed network could not be removed from the preferred networks list.

This issue occurs on the new MD-settings page introduced in M59.

Considering the issue was on M59, I wonder if new UI/option is heavily used. I assume the summer break is a factor for low reports on M59. 

Is there a way/option to disable the UI for M60?

+Steven
@tbarzic: did the UI change (Forget button used to be disabled changed through the switch to MD I settings?

So, what's the intended behavior? Should managed users not be able to Forget networks configured through device policy?

We could do something similar to Steven's CL https://codereview.chromium.org/2856863010 to disable/hide the button in the UI if that's what we want, though the networkingPrivate API should be changed to error out I guess.

Thanks,
Pavol

There is definitely a UI bug where we show+enable the 'Forget' button for user policy networks but the button does not do anything; I can fix that, but it isn't high priority. It is tracked in  issue 733737 .

I'm not that familiar with device policy networks or the expected behavior, and reading above the expected behavior seems unclear.

Can someone please clarify what the exact behavior WRT 'forgetting' networks installed by device policy should be?

Same as  crbug.com/733737  - you shouldn't be able to "forget" networks set by enterprise policy

I thought this through a bit more and read through the bugs associated with https://codereview.chromium.org/2754903002.

1. In that CL, we do intentionally allow apps (specifically kiosk apps) to remove any user configuration for device-policy networks, just not the device configuration. It appears however that the behavior is not what one would expect.
2. Since we do not expose that level of detail, we should just disallow forgetting of any policy configured network.

So, we should keep this open and improve the behavior of (1), but in the meanwhile I will prioritize  issue 733737  and remove the 'forget' option in the UI for all policy configured networks.

Fix in the UI in  issue 733737 .

Lowering priority since this is now just a matter of figuring out how best to improve the behavior when a kiosk app removes configuration from the user profile (which may just be an extra comment in the code).

Thank you for the fast UI fix Steven!

Agree with Comment 22:
> 2. Since we do not expose that level of detail, we should just disallow forgetting of any policy configured network.

This is also how I'd read the description of bug 705024.

Removing RBS and target proper solution in M61 based on c#24
Feel free to re-add the m60 labels if worth evaluating for merge when fix is available 

Thanks all.  crbug.com/733737  fix addresses the immediate concern.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.