Issue metadata
Sign in to add a comment
|
Enrollment with invalid domain is rejected due to licenses |
||||||||||||||||||||||
Issue descriptionChrome Version: M63.0.3239.11 dev kip OS: ChromeOS 10032.7.0 What steps will reproduce the problem? After wiping/recovery a device, attempt to enroll with a Gmail address which is ineligible. What is the expected result? "This user account is not eligible for the service." What happens instead? "Oops! The system failed to load available licenses." The rejection reason should not be related to licenses. No issue as checked with M62.0.3202.63 9901.49 beta daisy.
,
Oct 20 2017
,
Jun 1 2018
I confirm that the issue still exists in M-68. Chrome OS: 10718.9.0 Chrome: 68.0.3440.11 Device: Kip
,
Jun 5 2018
The error happens during license check (which client still sends request for even though we never launched the feature). Server sends back same error code (403) for non-Dasher users as it sends for registration request (actually user permission check is shared between two operations). What I suspect happens is licensing screen always displays the same error message. If that is true, we can't even disable licensing feature server-side, as that would be another error code resulting in the same screen. Suggest to verify my error handling assumptions and then stop pinging server to check licenses, or fix error handling on the client.
,
Jun 12 2018
OK, so it's basically a bad error message if you try to enroll with a gmail account.
,
Jun 26 2018
,
Jun 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/edb06ac93c04f61b4864b59b8a701b3d841932fd commit edb06ac93c04f61b4864b59b8a701b3d841932fd Author: Denis Kuznetsov <antrim@google.com> Date: Tue Jun 26 15:22:52 2018 Add extra check if device management is supported to License Check request. NOPRESUBMIT=true Bug: 776484 Change-Id: I13e112181571580052846cd24935284955e15768 Reviewed-on: https://chromium-review.googlesource.com/1090720 Commit-Queue: Denis Kuznetsov <antrim@chromium.org> Reviewed-by: Lutz Justen <ljusten@chromium.org> Cr-Commit-Position: refs/heads/master@{#570411} [modify] https://crrev.com/edb06ac93c04f61b4864b59b8a701b3d841932fd/chrome/browser/chromeos/policy/enrollment_handler_chromeos.cc [modify] https://crrev.com/edb06ac93c04f61b4864b59b8a701b3d841932fd/chrome/browser/chromeos/policy/enrollment_handler_chromeos.h [modify] https://crrev.com/edb06ac93c04f61b4864b59b8a701b3d841932fd/components/policy/core/common/cloud/cloud_policy_client.cc [modify] https://crrev.com/edb06ac93c04f61b4864b59b8a701b3d841932fd/components/policy/core/common/cloud/cloud_policy_client.h [modify] https://crrev.com/edb06ac93c04f61b4864b59b8a701b3d841932fd/components/policy/core/common/cloud/cloud_policy_client_unittest.cc
,
Jun 26 2018
,
Jun 28 2018
Verified fixed, attempt to enroll with a Gmail address displays the correct error message: "This user account is not eligible for the service." (see attached screenshot). Chrome OS: 10825.0.0 Chrome: 69.0.3475.0 Device: Nautilus |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krishna...@chromium.org
, Oct 19 2017Status: Available (was: Untriaged)