Fix YAPS failures due to enabled policy for login screen apps () |
|||||
Issue descriptionYAPS (the test enterprise policy server) currently fails to process any device policy request after the user session starts: HTTP 400 "Unknown policy type google/chromeos/signinextension" YAPS should be fixed to ignore the new policy type instead, or maybe even ignore all unknown policy types. (The latter would be simpler for future changes, but the former is closer to how the production DMServer works currently.)
,
Feb 20 2017
The symptoms for the issue are: at the chrome://policy page the status for Device policies displays: "Status: Invalid request or request parameters"
,
Mar 4 2017
This impacts testing of crbug.com/373324 -- FR - Enterprise Device Policy to set Language / Input Methods for Sign-In Screen. This issue starts to occur on 58.0.3011.0;9287.0.0.
,
Mar 4 2017
I will try to make it work on Monday (one of the CLs stuck in the code review).
,
Mar 4 2017
Verified the issue started on 58.0.3011.0;9287.0.0 dev cave ; no issue on 58.0.3011.0;9286.0.0 dev cave and earlier. Screenshot and log files attached.
,
Mar 7 2017
,
Mar 8 2017
I can confirm that Device Policy fetch works for me again (using 59.0.3033.0 BTW). Thanks for fixing this!
,
Mar 10 2017
Verified no issue in 58.0.3029.9:9334.4.0 beta on reks.
,
Mar 13 2017
@emaxx, Thank You for fixing this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by emaxx@chromium.org
, Feb 17 2017