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

Issue 685328 link

Starred by 4 users
Status: Archived
Owner:
█ bustamante@chromium.org
Last visit > 30 days ago
Closed: Dec 20
Cc:
vkasatkin@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Auto Detect Proxy Mode in Chrome Management Policy not Detecting System Settings

Reported by bsh...@mercuryprint.com, Jan 25 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
Steps to reproduce:
1. In GSuite configure DeviceManagement -> Chrome -> UserSettings -> Network -> Proxy Settings to Proxy Mode "Always Auto Detect the Proxy". 
2. Apply this setting to an OU
3. Create a User as a Member of this OU
4. On a Windows or MAC OS enable the Proxy Settings from Internet Options (or Network Preferences). The setting should include the use of a PAC file at a local URL.
5. On this Client machine open Chrome and check proxy settings using chrome://net-internals/#proxy
- Proxy System settings are correctly detected
6. Now login to Chrome using the User (and Policy) created in Steps 2 & 3
- Proxy System settings are NOT Correctly detected

What is the expected behavior?
When GSuite Chrome policy is set to "Always Auto Detect the Proxy", I expect Chrome to Detect the Proxy system settings.

What went wrong?
The policy is set in Chrome, but does not detect the system settings

Did this work before? Yes unknown

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 24.0 r0

GSuite support suggests that the Proxy settings are configured for "Always use the Proxy auto-config specified below". While this is a Workaround, it does not address the possible in bug in Chrome when receiving policy instructions from GSuite.
Chrome Policy.PNG
227 KB View Download
Proxy Comparison.PNG
491 KB View Download
proxy correct no login.PNG
82.6 KB View Download
proxy incorrect after login to chrome.PNG
110 KB View Download

Comment 1 by davidben@chromium.org, Jan 25 2017

Components: Internals>Network>Proxy

Comment 2 by vkasatkin@google.com, Jan 28 2017

Cc: vkasatkin@google.com
Labels: M-55 Hotlist-Enterprise

Comment 3 by vkasatkin@google.com, Jan 31 2017

Labels: -M-55 M-56
Owner: bustamante@chromium.org
Status: Untriaged (was: Unconfirmed)
I was able to reproduce with my test account in Windows and Chrome ver. 56.
Here are the screenshots and net-internal logs:  https://drive.google.com/drive/folders/0By9xEkAUmm_cSU9GenhoMWl1elE?usp=sharing

Comment 4 by schere...@gmail.com, May 17 2018 

We are seeing the same issue on Chrome 65. Both "auto_detect" and "system" fail to properly recognize the the PAC configuration stored in HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\AutoConfigURL

Comment 5 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Comment 6 by sylcat@google.com, Dec 14 

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 7 by sylcat@google.com, Dec 20

Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.
►

Sign in to add a comment