Issue metadata
Sign in to add a comment
|
Camera doesnot turn on after reboot for QR code login. |
||||||||||||||||||||||
Issue descriptionGoogle Chrome: 69.0.3497.14 Platform : 10895.5.0 Firmware : Google_Coral_10068.57.0 Setup a. Ensure the following device policies are set: i. LoginVideoCaptureAllowedUrls - URL pattern which matches IdP auth page (e.g. http://clever.com) ii. ‘Show user names and photos on the sign in screen’ - never iii. ‘AllowScreenLock’ - False iv. ‘Lock screen on sleep’ - True, lock screen Steps To Reproduce: 1. Enroll device into a domain which supports QR code based SSO. 2. After idling for 3 min on capture screen, device returns to SAML page. a. Boot device and click Next on SAML interstitial page. b. See that video capture is enabled. Expected Result: Video capture for QR login should be seen after reboot Actual Result: Video capture is not shown for QR login after reboot. How frequently does this problem reproduce? Always What is the impact to the user, and is there a workaround? If so, what is it? clear tpm and re-enrolling device will turn on camera for QR login. Additional Information: 1. Issue is also seen with Slippy (Falco) device. 2. Issue is not reproducible on versions a. Google Chrome 68.0.3440.78 Platform 10718.64.0-18.07.25 b. Google Chrome 67.0.3396.99 Platform 10575.58.0-18.06.23 Attached screenshot and logs.
,
Jul 27
Kevin no longer works on Chrome. Please reassign to someone else.
,
Jul 30
Adding some more labels
,
Jul 30
I'm going on vacation soon, so if it's real release blocker, someone else should own it now. Assigning to Maksim as he had experience with SAML. +Xiyuan for awareness from login UI team.
,
Jul 30
chchakrapani@: Could you please attach the dump of all policies from the chrome://policy page? To be sure I can reproduce exactly the same setup on my machine.
,
Jul 30
+jdufault After reboot, views-based login screen will be used. Login webui will be hosted in a webui dialog. I wonder whether that is related.
,
Jul 30
From the log (chrome_20180726-180235) in the original report: [1184:1184:0726/180253.827854:ERROR:web_contents_delegate.cc(175)] WebContentsDelegate::CheckMediaAccessPermission: Not supported. [1184:1184:0726/180253.966760:ERROR:web_contents_delegate.cc(165)] WebContentsDelegate::RequestMediaAccessPermission: Not supported. So it is related to hosting the login webui in a dialog in views based login. The WebDialogView is a content::WebContentsDelegate and we need to hook it with MediaCaptureDevicesDispatcher like WebUILoginView. Maybe create a subclass a WebDialogView and use it in [1] [1] https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/ui/oobe_ui_dialog_delegate.cc?rcl=c4a655f41b500eacf31358c87ea09b1354ee6567&l=66
,
Jul 30
,
Aug 16
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cd4b0fafeb6546618f80b8e521d278db027a6f82 commit cd4b0fafeb6546618f80b8e521d278db027a6f82 Author: Quan Nguyen <qnnguyen@chromium.org> Date: Thu Aug 16 18:45:34 2018 cros: Implement media access permissions in OOBE dialog. In order to enable webcam-based login (e.g. QR code signin), the OOBE web dialog now implements RequestMediaAccessPermission and CheckMediaAccessPermission. Bug: 868188 Change-Id: I4de25b3b194d2ecc207ca9ff1866809ad357b55c Reviewed-on: https://chromium-review.googlesource.com/1178111 Reviewed-by: Jacob Dufault <jdufault@chromium.org> Commit-Queue: Quan Nguyen <qnnguyen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583759} [modify] https://crrev.com/cd4b0fafeb6546618f80b8e521d278db027a6f82/chrome/browser/chromeos/login/ui/oobe_ui_dialog_delegate.cc
,
Aug 16
Should be fixed now.
,
Aug 24
Google Chrome: 70.0.3530.0 Platform: 10994.0.0 Falco Observation : Camera turns on after reboot for QR code login. Thanks for the fix :) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by grt@chromium.org
, Jul 27Labels: Enterprise-Triaged
Owner: cernekee@chromium.org
Status: Assigned (was: Untriaged)