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

Issue 832198 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Bluetooth pairing persists on shared machines

Project Member Reported by jparente@google.com, Apr 12 2018

Issue description

Description:
Allow policy that would limit Bluetooth device pairings to individual users instead of devices. Alternatively drop Bluetooth pairings when a new user logs in.

Use case:
A primary enterprise use case for ChromeOS devices is as loaners and shared devices. Ideally devices should be shared with as little human intervention as possible meaning that policies should be able to control the level of customization that an individual user can do to a device. With Bluetooth one user can pair mice, headsets, etc and they remains paired to that device even if that device has been passed to another user. This creates the undesired effect of those BT devices reconnecting to the shared device unexpectedly.

Motivation:
Our team manages the Google Open Source project "Grab n Go Loaners" (github.com/google/loaner) which is a low-touch ChromeOS loaner solution. We've had user reports that this is a problem. I can imagine as the shared use case grows internally and externally this might become a bigger problem.

Existing workarounds:
You can disable Bluetooth on shared devices but that makes it difficult for users that have specific needs (perhaps they rely on Bluetooth accessibility devices for example).

 
Cc: r...@chromium.org ortuno@chromium.org dskaram@chromium.org
Components: OS>Systems>Bluetooth
Labels: Enterprise-Triaged

Comment 2 by mcchou@chromium.org, Apr 19 2018

Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
This seems to be setting Bluetooth power state management based on enterprise policy. Assign this to rkc@ for triaging.

Comment 3 by rkc@google.com, Jan 17 (6 days ago)

Owner: jhawkins@chromium.org
James now owns connectivity in Chrome OS UI, over to him.

Sign in to add a comment