Fix ForceBrowserSignIn not working with networking service.
The problem was that the old sign-in flow didn't work with networking service. This hasn't been converted to use DICE, which already works. There were two causes: -webRequest interception wasn't enabled for the few internal webui pages that are whitelisted for webRequest API -webRequest users don't see Set-Cookie headers for responses (since these were sent to the interceptor from the network process, and the IPC serialization removes Cookie headers) Bug: 887381 Change-Id: I4f0b598c1610cd3b11dcf01cdd4d43425f218a4f Reviewed-on: https://chromium-review.googlesource.com/1238720Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#593703}
Showing
Please register or sign in to comment