Issue metadata
Sign in to add a comment
|
Unable to sign into browser using latest Canary with corporate / Okta enabled google accounts
Reported by
protonus...@gmail.com,
Aug 31
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. If you are already signed into the browser with a corporate / Okta enabled google account - you are unable to use this google account for google services like Gmail. Every time you open gmail - it will sign you out a second later. Occasionally you'll see an error about already being signed into the browser elsewhere? 2. If you then sign out of the browser itself, or uninstall/reinstall - you can no longer sign back into the browser with this corporate google account. It allows you to sign in, but nothing happens afterwards. The browser is not actually signed in. It may be related to Okta 2FA, or just specifically corporate google accounts. 3. Signing into the browser with normal personal google accounts works just fine. 4. Reproduced this several times with a fresh install of the latest Canary. 5. Unable to reproduce this with Chrome Beta, or Chrome Stable. Works fine in these versions. What is the expected behavior? To be able to sign in to browser with corporate google accounts. What went wrong? Canary broke something in the latest build. This was working just fine up until the latest build. Did this work before? Yes Prior build of Canary Chrome version: 70.0.3538.0 (Official Build) canary (64-bit) (cohort: Clang-64) Channel: canary OS Version: 10.0 Flash Version: 24.0.0.189 internal-not-yet-present This has made Canary unusable for me. I've had to switch back to Stable Chrome or Beta.
,
Sep 3
Thanks for filing the issue.. The issue seems to be related to corporate / Okta enabled google accounts which is out of TE-scope. Hence adding TE-NeedsTriageFromHYD, for further triaging of issue. Thanks.!
,
Sep 26
Actually adding TE-NeedsTriageFromHYD
,
Oct 5
can you disable "enable network service" on Chrome://flags and see if this repros.
,
Oct 5
I tried adding Okta to a personal domain that uses GSuite. Here's what I tried but I couldn't repro. Am I missing a step or doing something in the wrong order? Each of the cases below (a/b/c) were done in a fresh chrome profile after browser reboot and with network service enabled. A) sign in to browser with gsuite login install okta extension sign in to okta, from their site try to open gmail (gmail opens) B) sign in to okta (not to google) install okta extension try it to open gmail app (works) try to turn on sync (works) c) install okta extension sign in to browser I then went into the GSuite settings in Okta and turned on SSO through SAML, and also turned on SSO in GSuite security settings. I tried the above 3 scenarios and still couldn't reproduce.
,
Oct 8
,
Oct 8
Marked as duplicate since this bug was on canary before Reilly's fix landed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Sep 2