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

Issue 674561 link

Starred by 9 users

Issue metadata

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

Blocking:
issue 665973



Sign in to add a comment

Allowing switching the release channel for users on secondary domains

Project Member Reported by emaxx@chromium.org, Dec 15 2016

Issue description

Currently, only users with _exactly_ the same domain as the enrollment domain are allowed to switch the release channel on the enrolled devices.
The corresponding pieces of code just perform the exact string comparison of the user's e-mail domain and the enrollment domain: see [1], [2].
This makes it impossible to switch the release channels when the secondary domains are used: e.g. the enrollment domain is example.org, and the user's domain is foo.example.org.

This should be probably relaxed to allow users belonging to secondary domains to switch the channel too.

It seems that this could be achieved by checking against the user_manager::User::IsAffiliated method instead of doing e-mail parsing and domain comparison.

[1] https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/settings/about_handler.cc?l=115
[2] https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/help/help_handler.cc?l=117
 

Comment 1 by emaxx@chromium.org, Dec 15 2016

Cc: -atwilson@chromium.org
Owner: atwilson@chromium.org
Assigning to Drew for prioritization.
Cc: atwilson@chromium.org
Owner: mdrasner@chromium.org
Reassigning to Matt to roll this into his "support migrating primary -> secondary domains" list of task items.

Absolutely agreed that we should restrict to affiliated users rather than checking domain names.

Comment 3 by emaxx@chromium.org, Mar 2 2017

Blocking: -665973

Comment 4 by emaxx@chromium.org, Mar 2 2017

Blocking: 665973
Cc: monachow@chromium.org dskaram@chromium.org
 Issue 665973  has been merged into this issue.
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 8 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by dskaram@google.com, Mar 8 2018

Status: WontFix (was: Untriaged)
Unlikely to fix in the next year. Closing as Won'tFix.
Labels: Hotlist-GoodFirstBug
Status: Assigned (was: WontFix)
Keeping this since it's a nice noogler bug.
Cc: -atwilson@chromium.org mdrasner@chromium.org
Owner: atwilson@chromium.org
Owner: olsen@chromium.org

Sign in to add a comment