Issue metadata
Sign in to add a comment
|
Unable to enterprise enroll device |
||||||||||||||||||||||||
Issue descriptionChrome Version: 71.0.3544 Chrome OS Version:11055.0.0 Chrome OS Platform: Kevin/Caroline Network info: GoogleGuest Steps To Reproduce: (1)Flash latest ToT build (2)Attempt to enterprise enroll device (3) Expected Result: Device should successfully enroll into enterprise domain Actual Result: Unable to enroll device. Error message "Oops! The system failed to authorize API access for this device" How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always What is the impact to the user, and is there a workaround? If so, what is it? wont be able to enroll device into domain Please provide any additional information below. Attach a screen shot or log if possible. End user is able to use Guest session or able to log in as a user For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Sep 12
Attempted to enroll device in different test domains. Same error message is shown across all test domains.
,
Sep 12
,
Sep 12
same problem is being observed on veyron_tiger 11058.0.0
,
Sep 13
Adding more to the CC since this was tagged as a P0 Dev blocker with 2 people on the cc and no triage..... Hoping we can identify the proper owner(s). Also, possible this is related to crbug/883376? Thanks!
,
Sep 13
Sorry, meant to ask if it's a DUP of crbug/882866 in #5
,
Sep 13
Cross posting from https://crbug.com/882866 . The issue is in Chrome in commit https://crrev.com/978c0e67732f7829611e050602dea4e714225ee8 which has already been backed out from Chrome master. Unfortunately, CrOS is still pinned to a version of Chrome from the small time frame where the bad commit had landed but not been reverted. Picking up a new snapshot of Chrome should solve the problem.
,
Sep 13
,
Sep 13
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vaandres@chromium.org
, Sep 12