New issue
Advanced search Search tips

Issue 893546 link

Starred by 1 user
Status: Closed
Owner: ----
Closed: Oct 17
Cc:
ibezmenov@chromium.org
jayhlee@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Devices REST api always returns orgUnitPath as /, even if device is enrolled under specific org unit

 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
Platform: 10895.56.0 (Official Build) stable-channel snappy

Steps to reproduce the problem:
1. Enroll Chrome device under user which is present under some org unit.
2. Device got enrolled and we are able to see it on Google admin console.
3. Hit the REST API to fetch chrome devices https://www.googleapis.com/admin/directory/v1/customer/my_customer/devices/chromeos
"orgUnitPath" field should contain the path of specific org unit but it always return it as /

What is the expected behavior?
In REST API value of orgUnitPath should be users org unit under which device got enrolled.

What went wrong?
Devices REST api always returns orgUnitPath as / instead of users org unit path under which device got enrolled

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 69.0.3497.95  Channel: stable
OS Version: 69.0.3497.95
Flash Version: 

Screenshots explains below things:
1) Shows the Chrome device screen with user name under which device got enrolled
2) Shows the Google admin console with user present under some org unit.
Chrome_device.png
3.4 MB View Download
User_account.JPG
117 KB View Download

Comment 1 by jayhlee@google.com, Oct 11

Cc: jayhlee@google.com
Components: Enterprise>Enrollment
Labels: -Arch-x86_64 Hotlist-Enterprise
please confirm that under:

admin.google.com > Devices > Chrome management > User settings > Enrollment Controls > Device Enrollment > Place Chrome devcie in user organization during manual enrollment

the setting should be "Place Chrome device in user organization"

please also be aware that as described in the help article:

https://support.google.com/chrome/a/answer/2657289?hl=en#enrollmentcontrols

"Note: This policy will only take effect if the device is being enrolled into the domain for the first time or the device was previously deprovisioned."

just wiping and re-enrolling the device w/o deprov will not move the device.

Comment 2 by ibezmenov@chromium.org, Oct 15

Labels: Needs-Feedback

Comment 3 by ni...@ps-mobility-test.int.hp.com, Oct 17 

Thanks for your feedback. Its working as expected now. We can close this ticket
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 17

Cc: ibezmenov@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ibezmenov@chromium.org, Oct 17

Status: Closed (was: Unconfirmed)
Thanks for the info! Closing this based on c#3.
►

Sign in to add a comment