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

Issue 906661 link

Starred by 4 users
Status: Duplicate
Merged: issue 904837
Owner:
hendrich@chromium.org
Closed: Nov 20
Cc:
marcore@chromium.org
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Configured user (different domain from device) network not connecting automatically

Project Member Reported by marcore@chromium.org, Nov 19 
ChromeOS version: 70.0.3538.76
 https://drive.google.com/open?id=1zYphQwwE0-vt8kcyZoKpBUR1Z0B7jc7f
ChromeOS device model:  Any
Case#: 17197874

Description: the user wifi is not autoconnecting when logged on a device enrolled in another domain


Steps to reproduce: 
1) enroll a device in domainA
2) configure for the user in domainB one wifi to autoconnect (INSIDEB)

Current Behavior / Reproduction: 
every time the user has to select the network INSIDEB
Expected Behavior: 
autoconnect to network INSIDEB

Drive link to logs: https://drive.google.com/open?id=1cC2qFspLTzPJjLDEQHFcxRPYrx6ix3sH
policy: 
PDF: https://drive.google.com/open?id=1ETZ16_iDjoQvqeNi9II5od56ezZ4bntt
json: https://drive.google.com/open?id=1GgjjuSjCynd2AkwSONkqlQjsFVpl8bo_

5:25 already logged in as domainB, connect manually to INSIDEB
logout
5:26 switch to INSIDEA on login screen
5:27 login with user on domainB (no autoconnect to INSIDEB)
5:27 click on INSIDEB connected

on  https://crbug.com/774507#c34  (proxy settings) it's written:
... where we do not apply device policy proxies unless the user is in the device's domain or the use_shared_proxies pref is set.
it's possible that also the autoconnect has the same logic ?

Comment 1 by pmarko@chromium.org, Nov 19

Owner: hendrich@chromium.org
Alex, would you please take a look tomorrow? This seems similar to another report that came in lately.

Comment 2 by hendrich@chromium.org, Nov 20 

 Bug 904837  sounds similar (CL with a fix is in review), but that also only happens once. As soon as the user manually connects to the network from the user policy (INSIDEB), the has_ever_connected criteria is equal for both networks and INSIDEB should auto-connect.
Is this behavior reproduciable multiple times? If yes, then this might be a different problem or we're not saving has_ever_connected correctly.

Comment 3 by atasheva@google.com, Nov 20 

Hi Hendrich@, 

The behavior is exactly as you described it. If the customer manually connects to the user level policy once, they can reboot the device and it will continue to auto-connect to the network.

It's good to know that it's the same issue and the expected behavior is not different due to the fact that there are two domains involved. 

Thanks.

Comment 4 by hendrich@chromium.org, Nov 20

Mergedinto: 904837
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment