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

Issue 772319 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Autodetected proxies should not overwrite configured proxies for managed networks

Project Member Reported by atwilson@chromium.org, Oct 6 2017

Issue description

1) Configure a user with the default "Autodetect Proxy" setting.
2) At signin screen, select a policy-configured device wide network with a proxy
3) Sign in to the user.
4) Find that you are still connected to this network, but you lose the proxy setting (it's replaced with the autodetected proxy).
5) If the user's proxy setting is set to "allow user to configure" then it's fine - the network-defined proxy is maintained.

I'm thinking we should give priority to the network-defined proxy in pretty much all cases other than an explicitly configured user proxy.
 
Cc: msnoxell@chromium.org
Status: Untriaged (was: Unconfirmed)
Status: Assigned (was: Untriaged)
Owner: ultrotter@chromium.org
Labels: Hotlist-GoodFirstBug
Owner: askaraitzhan@google.com

Sign in to add a comment