Proxy authentication at startup has issues with saving usernames/passwords and with waiting for authentication to load content
Reported by
k...@luminance.org,
Mar 1 2018
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Example URL: n/a Steps to reproduce the problem: 1. Keep tabs open that rely on username+password proxy authentication to be accessed 2. Exit, with 'continue where you left off' enabled 3. Open Chrome again What is the expected behavior? The authentication popup should appear and loading of proxy-required pages should halt until authentication is completed or fails What went wrong? Sometimes Chrome begins loading the pages before the proxy authentication popup is closed, which results in proxy unauthenticated error messages appearing in place of the pages. Frequently the authentication popup appears and partially blocks page loads, but the saved username/password are forgotten (the input fields are empty). If I terminate Chrome and start it again the username/password memory then works. Did this work before? N/A Chrome version: Version 64.0.3282.186 (Official Build) (64-bit) Channel: stable OS Version: 10.0 Flash Version: Pages also still partially load without authenticating against the proxy, but in this case they don't produce an unauthenticated error. I can't tell whether they're being loaded directly from cache (okay, probably?) or whether the proxy is being briefly circumvented (not okay). I would assume it is the former. You can manually reproduce the empty username/password field bug by canceling the first authentication prompt (if it remembered your username/password). Typically if you cancel again, suddenly it remembers the credentials. Screenshots attached. (You can also see that content is being loaded before proxy authentication has occurred, but I think it's probably loading from cache) I'm using a squid proxy over http2, fwiw.
,
Mar 1 2018
,
Mar 1 2018
Unable to reproduce this issue on reported version 64.0.3282.186 using Windows 10 with steps mentioned below. 1. Enabled proxy and saved credentials. 2. Now opened 2 pages which asks credentials and also selected 'continue where you left of' option. 3. No closed and opened chrome again, observed authentication dialog with autofilled date, cancelled it and observed again proxy authentication dialog with date. Attaching screencast for reference. @Reporter: Please check the video and let us know if we miss anything. How frequently is this happening? Also please check on fresh profile which do not have any extensions or apps and by resetting all flags from chrome://flags. This info would help us in triaging the issue further. Thanks!
,
Mar 1 2018
It won't reproduce on the first try like that, I see it maybe a dozen times a day - if I just start and exit repeatedly right now it doesn't happen. It's probably a race condition. The prompt pops up and then is replaced by a new copy of the prompt with the saved credentials missing. Incidentally, I see the authentication prompt every time I start Chrome even though I've saved the username/password, but you don't. Is the prompt not supposed to appear, and that's the root of my issues? Is there a setting I should change to make the prompt not open? I checked and my saved passwords in Chrome have an entry for the proxy.
,
Mar 1 2018
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
,
Mar 3 2018
Here is a screen recording of the issue. I believe it has something to do with the startup page attempting to do a timeout/logged-out redirect - if I launch Chrome (with this tab remembered) after a few hours of non-usage, this bug happens, but if I exit and relaunch immediately it doesn't. You can see the auth window opens with saved credentials, then immediately closes and reopens with the credentials gone.
,
Jun 21 2018
kg@ - Could you please upgrade chrome to latest stable #67.0.3396.87 and please let us know if the issue still persists or not. The latest chrome builds can be downloaded from the below URL: https://www.chromium.org/getting-involved/dev-channel Thanks...!!
,
Jun 21 2018
,
Jun 22 2018
Still broken the same way.
,
Jun 22 2018
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
,
Jun 27 2018
We don't save auth information to disk (between normal restarts, or when saving a session). I don't think there's sufficient need to change behaviors here. CCing the session folks, in case they disagree.
,
Jul 5
As per comment#11 it is understood that the issue seems to be a Feature request, hence marking it as Untriaged and adding appropriate labels. Thanks!
,
Jul 5
This isn't a feature request, the feature is implemented and demonstrated in comment 3's video. This is a bug. The feature does not work correctly. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by k...@luminance.org
, Mar 1 2018