Device policy backing store in bad state on first login |
||||||
Issue descriptionOn a Linux build, at the first user login, the backing store is in bad state. After a restart, it works fine. It seems that enrollment doesn't leave the browser in the correct state.
,
Jan 9 2017
,
Jan 13 2017
On Linux, the status is "Invalid request or request parameters".
,
Jan 17 2017
Can't repro anymore. Probably this has been addressed in issue 677511 .
,
Jan 18 2017
Actually, I still see this.
,
Jan 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e30959a32e573cc2264bafe4ab57fc93c6a234af commit e30959a32e573cc2264bafe4ab57fc93c6a234af Author: tnagel <tnagel@chromium.org> Date: Wed Jan 18 19:55:13 2017 Chromad: Disable device attribute update after enrollment Attribute updates are not supported in Chromad, and disabling them allows to get rid of the CloudPolicyClient right after enrollment has finished. BUG= 677510 Review-Url: https://codereview.chromium.org/2640843002 Cr-Commit-Position: refs/heads/master@{#444444} [modify] https://crrev.com/e30959a32e573cc2264bafe4ab57fc93c6a234af/chrome/browser/chromeos/login/enrollment/enterprise_enrollment_helper_impl.cc
,
Jan 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/33d0fb8f91ec8be93f0bc56b63c67a9f2dcebec6 commit 33d0fb8f91ec8be93f0bc56b63c67a9f2dcebec6 Author: tnagel <tnagel@chromium.org> Date: Wed Jan 18 20:07:49 2017 Don't start device cloud policy connection after Chromad enrollment After Active Directory enrollment, don't start the connection for the device cloud policy manager (as would happen for cloud management). Also ensure that TryToCreateClient() doesn't start a client, as could e.g. be triggered by OnStoreLoaded(). BUG= 677510 Review-Url: https://codereview.chromium.org/2642793002 Cr-Commit-Position: refs/heads/master@{#444451} [modify] https://crrev.com/33d0fb8f91ec8be93f0bc56b63c67a9f2dcebec6/chrome/browser/chromeos/policy/device_cloud_policy_initializer.cc
,
Jan 19 2017
,
Jul 6 2017
bulk Verify of Chromad V1 bugs |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tnagel@chromium.org
, Jan 9 2017