New issue
Advanced search Search tips

Issue 828906 link

Starred by 2 users
Status: Assigned
Owner:
pmarko@chromium.org
Cc:
pastarmovj@chromium.org
hendrich@chromium.org
rdevlin....@chromium.org
mea...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Make --whitelisted-extension-id command-line switch lift policy location restrictions

Project Member Reported by pmarko@chromium.org, Apr 4 2018 
Extend the functionality of the --whitelisted-extension-id switch to also lift "location": "policy" restrictions for the specified extension.

This is intended to make development of extensions that will use APIs restricted to force-installed extensions easier.

Make sure we don't lift other restrictions, such as "location": "component".

Comment 1 by mea...@chromium.org, Apr 5 2018 

To confirm, whitelisted-extension-id is currently only used for testing, is that correct? E.g. we don't launch a process with this flag to run a component extension or anything similar?

Comment 2 by rdevlin....@chromium.org, Apr 5 2018 

We don't currently rely on this flag to run chrome normally.  It is used for testing, but both for chrome unit/browser tests and for teams developing extensions and testing them on release builds of chrome.

Does that clear it up?  Or did I misunderstand the question?

Comment 3 by pmarko@chromium.org, Apr 6 2018

Cc: hendrich@chromium.org

Comment 4 by chrismoon@google.com, Apr 6 2018 

Will this also allow chrome.Enterprise.platformKeys to be ran? Not only does it have to be force-installed, it also needs a bit flipped in Admin Console to allow it to be ran. 

https://support.google.com/chrome/a/answer/6080885?hl=en
►

Sign in to add a comment