Chromad first user login crashes |
|||
Issue descriptionLogging the first user into a Chromad managed device crashes because session_manager thinks the device is consumer owned and creates a policy key for that user.
,
Jan 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/df42f704203be9669f1ba9d17eaa95c2aa5f8d68 commit df42f704203be9669f1ba9d17eaa95c2aa5f8d68 Author: Thiemo Nagel <tnagel@chromium.org> Date: Thu Jan 12 16:26:31 2017 login: Don't create policy key for AD management Prevent session_manager from creating a keypair for the first user to log into an Active Directory managed device. BUG= chromium:680534 TEST=adding unittest, also tested manually Change-Id: I34ba30b7842aa6d2627593776afbe62dc64c417f Reviewed-on: https://chromium-review.googlesource.com/427760 Commit-Ready: Thiemo Nagel <tnagel@chromium.org> Tested-by: Thiemo Nagel <tnagel@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> [modify] https://crrev.com/df42f704203be9669f1ba9d17eaa95c2aa5f8d68/login_manager/session_manager_impl.cc [modify] https://crrev.com/df42f704203be9669f1ba9d17eaa95c2aa5f8d68/login_manager/session_manager_impl_unittest.cc
,
Jan 13 2017
,
Jul 6 2017
bulk Verify of older or not-user-facing Chromad bugs |
|||
►
Sign in to add a comment |
|||
Comment 1 by tnagel@chromium.org
, Jan 12 2017