New issue
Advanced search Search tips

Issue 709416 link

Starred by 3 users
Status: Verified
Owner:
rsorokin@chromium.org
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

chrome://flags empty

Project Member Reported by rsorokin@chromium.org, Apr 7 2017 
Ownership service does not work correctly on Active Directory devices. 
Now it loads owner key to identify the owner. This does not work for
Active Directory devices which does not contain the key.

One of the symptoms:
chrome://flags page is empty on AD devices. It waits on a callback from IsOwnerAsync which never get called.

Comment 1 by rsorokin@chromium.org, Jun 19 2017

Labels: -Pri-3 M-61 Pri-2
Owner: tnagel@chromium.org
Seems like the problem with /var/lib/whitelist/owner.key. It does not exist on chromad devices. Thiemo, maybe you know something about it?

Comment 2 by tnagel@chromium.org, Jul 26 2017

Owner: ----
Status: Available (was: Assigned)

Comment 3 by rsorokin@chromium.org, Jul 26 2017

Labels: -M-61 M-62
Owner: rsorokin@chromium.org

Comment 4 by ljusten@chromium.org, Sep 15 2017

Status: Assigned (was: Available)

Comment 5 by ljusten@chromium.org, Oct 18 2017

Labels: Pri-3

Comment 6 by ljusten@chromium.org, Oct 18 2017

Labels: -M-62

Comment 7 by rsorokin@chromium.org, May 4 2018

Labels: -Pri-3 Enterprise-Triaged M-68 Pri-2
Status: Started (was: Assigned)

Comment 8 by rsorokin@chromium.org, May 7 2018

Description: Show this description
Project Member

Comment 9 by bugdroid1@chromium.org, May 11 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d6ffafb0e4d693e38b9269a4263222c2eb2cb7a0

commit d6ffafb0e4d693e38b9269a4263222c2eb2cb7a0
Author: Roman Sorokin <rsorokin@chromium.org>
Date: Fri May 11 10:31:38 2018

Ownership service to check if device is managed.

Now it loads owner key to identify the owner. This does not work for
Active Directory devices which does not contain the key.

BUG= chromium:709416 
TEST=manual

Change-Id: I44469a2f0b68910490ffa45cef14be6e53ff1cae
Reviewed-on: https://chromium-review.googlesource.com/1046602
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Roman Sorokin <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557835}
[modify] https://crrev.com/d6ffafb0e4d693e38b9269a4263222c2eb2cb7a0/chrome/browser/chromeos/ownership/owner_settings_service_chromeos.cc
[modify] https://crrev.com/d6ffafb0e4d693e38b9269a4263222c2eb2cb7a0/chrome/browser/chromeos/ownership/owner_settings_service_chromeos.h
[modify] https://crrev.com/d6ffafb0e4d693e38b9269a4263222c2eb2cb7a0/components/ownership/owner_settings_service.h

Comment 10 by rsorokin@chromium.org, May 11 2018

Status: Fixed (was: Started)

Comment 11 by ibezmenov@chromium.org, Jun 6 2018

Status: Verified (was: Fixed)
Verified, chrome://flags page is not empty on AD devices (see attached screenshot).

Chrome OS: 10757.0.0
Chrome: 69.0.3451.0
Device: Santa
Screenshot 2018-06-06 at 3.01.33 PM.png
97.4 KB View Download
►

Sign in to add a comment