Chrome sign-in/sync - proxy stops working

[gerardsweeney]

Hello, all..

 

This is probably something REALLY simple, and my coffee deficiency is showing.

 

Up until now, we've used GPO to remove the option to allow folk to sign into Chrome.

Now, however - as is the way with things - we need to look at enabling it to allow Staff to use an extension which is registered to our central email domain account.

It only works if you're logged into Chrome with a valid email domain.

 

 

Anyhoo.. Onto the actual problem

 

As a test, I've removed the GPO that prohibits the sign in.

I login into Chrome with my relevant credentials (it takes me to the main login page).

I select "Link".

And then I can't browse the WWW.

If I look at Chrome settings, proxy, it's still all good - using the System proxy settings.

As soon as I go into Settings and logout, WWW works again.

 

We're behind authenticated proxy (WebSense/ForcePoint).

 

Our proxy Infrastructure person isn't in this week (yay), so I'm kind of guessing here that the proxy is either being fed bobbins details, or that it isn't actually using the System proxy settings...

Does Chrome not send the user credentials of the logged on user when using a linked/sync'd account?

 

Cheers,

Gerard

[free780]

Have you tried setting your proxy settings in the Chrome GPO rather than relying on the system setting. Also are you using WPAD as chrome looks for this unless disabled by Policy.

[gerardsweeney]

Sussed it.

 

Turns out that our Chrome GPO didn't have a setting telling it to use the system proxy settings.

It appears that if you don't have that enabled, normal "non-signed-in" users are absolutely fine - it uses system proxy.

If you sign in, though, it tries to go out direct.

So I just updated the GPO to force it to use system proxy - and all seems well.