New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 871203 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Sep 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

New OOBE flow for license packaged devices

Project Member Reported by hendrich@chromium.org, Aug 6

Issue description

If the user tries to enroll a device with a consumer account, the server should return a 403 error code. This response should also contain information whether the device's serial number is whitelisted for license packaging.

A) If the device has no packaged license: Display the existing "This user account is not eligible for the service" message.
B) If the device has a packaged license, Display a new message
"Your device includes a Chrome license, but your username is not associated with an Admin console. Please create an Admin console to proceed with enrollment.

Note: If you choose to use your own domain to create a new Admin console, you must also complete domain verification after signup.

[Display signup option (link to Cloud Identity signup form in embedded guest session)]"


PRD: go/cros-lp-oobe
 
Components: Enterprise>Enrollment UI>Shell>OOBE Enterprise
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 27

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

commit 9fb2b022bbcc786ed370c6ac7cbc83b65af29352
Author: Alexander Hendrich <hendrich@chromium.org>
Date: Mon Aug 27 12:14:08 2018

New error message when a consumer account with packaged license enrolls

This CL adds handles the status code 417 from DMServer on an enrollment
request, which occurs when the user has a packaged license and tries to
enroll with a consumer account. The new error message hints the user to
create an admin console.

Bug:  871203 
Change-Id: I9ddf696a252809f80104502b6df6744b1620e009
Reviewed-on: https://chromium-review.googlesource.com/1180961
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Alexander Hendrich <hendrich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586239}
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/chrome/app/chromeos_strings.grdp
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/chrome/browser/chromeos/login/enrollment/enterprise_enrollment_helper_impl.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/chrome/browser/chromeos/policy/enrollment_handler_chromeos.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/chrome/browser/ui/webui/chromeos/login/host_pairing_screen_handler.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/browser/cloud/message_util.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/cloud_policy_constants.h
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/cloud_policy_refresh_scheduler.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/cloud_policy_refresh_scheduler_unittest.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/device_management_service.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/device_management_service_unittest.cc
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy/core/common/cloud/enterprise_metrics.h
[modify] https://crrev.com/9fb2b022bbcc786ed370c6ac7cbc83b65af29352/components/policy_strings.grdp

Status: Fixed (was: Assigned)
Status: Assigned (was: Fixed)
Hi Alexander,

In the order to verify this bug, could you please provide an instruction how to install a packaged license onto device?

Thanks,
Ivan
Cc: kathrelk...@chromium.org ibezmenov@chromium.org sjoe@chromium.org
Status: Verified (was: Assigned)
I was able to verify this using YAPS and error codes (403, 417) emulation (see attached screenshots).

Chrome OS: 11021.18.0
Chrome: 70.0.3538.21
Device: Snappy

However, the device verification based on the whitelisting is pending and will be performed when server-side work will be done.
Screenshot 2018-09-17 at 2.16.02 PM.png
38.0 KB View Download
Screenshot 2018-09-17 at 2.15.20 PM.png
56.0 KB View Download
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 23

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

commit dd323fea0b74017e1b79e6ab12c8b34534cfdfa7
Author: Alexander Hendrich <hendrich@chromium.org>
Date: Tue Oct 23 17:45:52 2018

Add enum description for 'consumer account with packaged license'

This is a follow-up CL for 1180961 that added a new enum value.

Bug:  871203 
Change-Id: If24076a45be092ea1081a05c7fd5ec5b1a42f9b2
Reviewed-on: https://chromium-review.googlesource.com/c/1296600
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Alexander Hendrich <hendrich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602004}
[modify] https://crrev.com/dd323fea0b74017e1b79e6ab12c8b34534cfdfa7/components/policy/core/common/cloud/enterprise_metrics.h
[modify] https://crrev.com/dd323fea0b74017e1b79e6ab12c8b34534cfdfa7/tools/metrics/histograms/enums.xml

Sign in to add a comment