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

Issue 604593 link

Starred by 4 users
Status: Verified
Owner:
█ vidster@chromium.org
Last visit > 30 days ago
Closed: Dec 11
Cc:
█ juanra...@chromium.org
█ sdavern@chromium.org
█ sduraisamy@chromium.org
█ gbirtchnell@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

Auto-whitelist safe platform extensions for Public Sessions

Project Member Reported by johnsonrichard@chromium.org, Apr 19 2016 
Description:
Create a criteria or whitelist to allow extensions in public sessions

Use case:
Currently have 2 large APAC customer that would like the ability to push extensions into Public sessions.

Motivation:
Both Customers has over 500 Public session terminals and large number of CROS licenses 

Existing workarounds:
None

This is similar to https://bugs.chromium.org/p/chromium/issues/detail?id=470779, but for extensions

Comment 1 by scunning...@chromium.org, Apr 19 2016

Cc: juanra...@chromium.org sduraisamy@chromium.org
Status: Assigned (was: Untriaged)
Please prioritize and assign.

Comment 2 by gbirtchnell@chromium.org, Apr 28 2016

Labels: Hotlist-Enterprise

Comment 3 by johnsonrichard@chromium.org, May 5 2016 

Polite Ping

Any update on this one?

Comment 4 by johnsonrichard@chromium.org, May 17 2016

Labels: -Pri-3 Pri-1
Changing to P1

Large Enterprise Customer requiring Extension with chrome.enterprise.deviceAttributes API in public session.

Requesting White-list criteria for customer to build ext that can be whitelisted.

Comment 5 by vidster@chromium.org, Jun 16 2016

Labels: PublicSessions-Whitelist

Comment 6 by atwilson@chromium.org, Dec 11

Status: Fixed (was: Assigned)
Fixed, managed guest sessions has no whitelist.

Comment 7 by chchakrapani@chromium.org, Dec 14

Status: Verified (was: Fixed)
Closing it as verified for now as per #c6.
Please provide steps if this requires manual verification. Thanks.!
►

Sign in to add a comment