Lock network configuration change for online Demo Mode |
||||||
Issue descriptionIf network is configured by the user during online Demo Mode setup, the configuration should be locked. The only way to change it is power-washing and setting up the device again. This restriction does not apply to the device that was transitioned from offline to online mode. Therefore is probably cannot be configured by policy only.
,
Jun 14 2018
Update: We want to implement a policy for that. Network configuration control will be implemented as a new Device Policy. We will add lockNetworkConfigUsedForEnrollment. The configuration will not be passed in a policy, instead the network chosen during OOBE/online enrollment of the device will be locked. Different demo mode configurations will need different values of the policy: Online - lockNetworkConfigUsedForEnrollment: true Offline - lockNetworkConfigUsedForEnrollment: false Derelict - lockNetworkConfigUsedForEnrollment: true We will need to load different policy blobs for Offline and Derelict mode during offline setup.
,
Jul 16
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Aug 24
,
Aug 28
As spoken offline, there is some more product side specification needed for this feature. Let's sync after M70 branch work is done. Some questions: 1. Should we only lock Wi-Fi network or other interfaces too? 2. What if multiple networks are connected during enrollment? 3. How to interact with existing policies? Eg. Should we allow enrollment network and networks listed by policy? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by agawronska@chromium.org
, May 14 2018