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

Issue 902337 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Error message using chrome://chrome-signin/?source=0 with SSO username

Project Member Reported by marcore@chromium.org, Nov 6

Issue description

Chrome version: 69.0.3497.92
OS version: Windows
Case#: 17323893

Description:
the message [ Login is failed. ClientLogin response cookies didn’t contain an auth code ] is shown when trying to login with SSO authentication at chrome://chrome-signin/?source=0 
the user is unable to login.

Steps to reproduce: 
configure the domain to use SSO
open chrome://chrome-signin/
Current Behavior / Reproduction: 
the message "Login is failed. ClientLogin response cookies didn’t contain an auth code" is shown
the user is not logged in
Expected Behavior: 
to be able to login

I've also found that this url is used in https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/signin/inline_login_ui_browsertest.cc and other unit test.
Bisect: 
Last Good 69.0.3493.3
First Bad 69.0.3494.0
still happening in 70.0.3538.77
on 71.0.3578.30 (actual beta) is fixed
on 72.0.3603.0 (actual Canary) is fixed

https://chromium.googlesource.com/chromium/src/+log/69.0.3493.0..69.0.3494.0?pretty=fuller&n=10000
it could be 
https://chromium.googlesource.com/chromium/src/+/1ba11572999c90d234c5e53fe7decb4bf7db1cf9

Video of the issue: https://drive.google.com/open?id=1toAdMf-7W265SUsSGxvgKvv2Bs8jA0oy
HAR file: https://drive.google.com/open?id=1JhuYA6weJouUZo8CvsH5bbHt5VAQQ85Q
 
Status: WontFix (was: Untriaged)
chrome://chrome-signin/?source=0 is no deprecated and logging in to Chrome happens via a different URL. Please use the UI buttons to start a Chrome sign-in flow and not copy/pasting this URL.

Sign in to add a comment