https://cdn.imges.link/images/c5fcefda0cbb3a560d615fa1b09a0c88.gif

Video of what happens.

Unable to reproduce the issue on win-10 using chrome reported version #70.0.3538.45 and latest canary #71.0.3569.0.
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened chrome and navigated to Settings.
2. Clicked on Turn on Sync and signed into account.
3. Observed that the account got synced without any issues.
Note: Tested by setting #network-service flag at chrome://flags to default/enabled/disabled. Everytime the signed in account got synced.

kalaria@ - Could you please check the issue on latest canary #71.0.3569.0 by setting #network-service flag at chrome://flags to enabled/disabled by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 891830.mp4 2.7 MB

	891830.mp4 2.7 MB View Download

Hello,

It was set to default. I set it to enabled and it still didn't work. It worked when I set it to disabled. Now its set back to default. Not sure what was causing the issue.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Also, note that I did that in Beta version and not Canary.

As per comment #4, it seems that google sign in sync worked properly when #network-service flag at chrome://flags is set to disabled.
Hence, requesting some one from Internals>Network team to please have a look into the issue and removing the Needs-Bisect label as the issue is not reproducible from TE-end.
kalaria@ - Could you please provide netlog dump by following steps in the below url:
https://www.google.com/url?q=https://www.chromium.org/for-testers/providing-network-details&sa=D&source=hangouts&ust=1538802784313000&usg=AFQjCNFMWz5xGGU3iWFy_ScDQ3-dsmnUkw

Thanks...!!

Hello,

I can replicate the issue on the machine. If I sign-off and try to relogin with #network-service enabled I run into the same issue again. 

The only way it works for me is to turn of #network-service and relog and turn it back on.

I took two dumps one with #network-service on and one with #network-service off.

Thanks

Deleted: chrome-net-export-log.json 18.2 MB

chrome-net-export-log.json 18.2 MB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Another log with network-service disabled which allows to login into google sync.

Also note that once I am signed off and #network-service is enabled it doesn't allow me to login into Gmail, calendar, drive either.

https://drive.google.com/open?id=19KuZUJ8pkthrdSToj3NkIWSHZoLEg-Ct - Can't attach it because the log is big 35 MB.

cc'ing jam and Dxie

Reilly: can you please take a look?

looking at the video by the reporter, it seems that the request is intercepted by an extension (looks like a blue circle on the corner). I'll figure out what that extension is and try to repro with that installed.

in the mean time, kalaria@gmail.com, can you let us know which extension you have installed? It seems there is a one that deals with sign in requests. If you can disable that one and give it a try, that'd help a lot.

looks like the user is using OKTA. 

Deleted: frame_123_delay-0.7s.gif 28.0 KB

	frame_123_delay-0.7s.gif 28.0 KB View Download

I created a new profile under Manage People and tried to log in see attached log. #networ-service is set to default.

Deleted: chrome-net-export-log.json 3.9 MB

chrome-net-export-log.json 3.9 MB View Download

kalaria@gmail.com:

Can you try the following:

Enable the network service in chrome://flags and disable Okta to see if you can log into sync?

kalaria@gmail.com: if you are blocked from your day-to-day workflow, please go to chrome://flags and set "enable network service" to disable. We are investigating this issue.

I have no clue how to disable okta. Its single sign-on probably set up in gsuites I am not running any addon. Yes, the workaround seems to work for now. 

Thanks

The Okta extension is using the webRequest API to intercept and modify requests. It is possible this is interacting poorly with the interception that the Chrome Signin code does for Google login pages.

This may also be a poor interaction with a domain configured for SAML login and not be Okta specific. Does our QA team have one of these set up for testing?

Copying my comment from https://bugs.chromium.org/p/chromium/issues/detail?id=879700#c5; if there's something I'm missing please let me know.


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.

Update: Reilly found out that:
1) this only happens in Beta, but not dev or canary (I was using canary)
2) this happens with and without the Okta extension installed

@kalaria: can you please try this with canary/dev and see if it works there?

One more note:
Since canary/dev work, I tried to bisect (with chromium):
-trunk works
-595531 and 595530 work (change that stopped sending non-navigation browser requests to webrequest)
-587811 (revision at which 70 branched) works

I could confirm that beta on Linux also doesn't work, while dev does. So I wonder if something got merged to beta branch which caused this to stop working?

Yes, it started happening after 2-3 Beta's ago from the current version. I will test out the dev/canary.

Ok good news is that Reilly went back in time and fixed this in https://chromium-review.googlesource.com/c/chromium/src/+/1207712, so we just need to merge that small cl.

Thanks past me! Requesting merge of the patch in comment 27 to M-71. This is code for the Network Service experiment and is not exercised with the Network Service disabled.

Ignore that. I see jam@ has requested merge on another issue.