New issue
Advanced search Search tips

Issue 808970 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Automated testing of Chrome ExtensionInstallForcelist policy with pytest-selenium

Reported by max.muel...@gmail.com, Feb 5 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Build an extension and do not upload it to the Chrome Web Store
2. Setup an environment so that this self-hosted extension is force-installed via the ExtensionInstallForcelist policy
3. Start Chrome via pytest-selenium (executing a .py script)

What is the expected behavior?
The extension is force-installed.

What went wrong?
If Chrome is started by the .py script, the extension is not installed.
If Chrome is started like a normal user would do it, the extension is force-installed.
This behavior occurs on the same machine.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 
Flash Version: 

The command line from the chrome://version tab:

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --cancel-first-run --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --disable-web-resources --enable-automation --enable-logging --force-fieldtrials=SiteIsolationExtensions/Control --ignore-certificate-errors --load-extension="C:\Users\Test1\AppData\Local\Temp\scoped_dir7780_3898\internal" --log-level=0 --metrics-recording-only --no-first-run --password-store=basic --profile-directory="\"Default\"" --remote-debugging-port=12568 --start-maximized --test-type=webdriver --use-mock-keychain --user-data-dir="C:\Users\Test1\AppData\Local\Temp\scoped_dir7780_516" --flag-switches-begin --flag-switches-end
 
Cc: pastarmovj@chromium.org
CC'ing the concern dev for further triage
Cc: devlin@chromium.org
Components: Platform>Extensions Tests>WebDriver
Adding the extensions and WebDriver labels for some visibility.

Do any of you know if WebDriver influences the installation of extensions like this per design or is this a bug?

In either way force installed extensions should not be allowed to be disabled by running with WebDriver enabled.
Labels: Enterprise-Triaged
Cc: nrpeter@chromium.org
I'm not very familiar with WebDriver.  I know that it has its own ability to load extensions, etc - maybe some of that is interfering with the policy?  The WebDriver team might be able to comment more.

+nrpeter FYI
The only thing that might be relevant from WebDriver side is it adds --load-extension switch to Chrome command line. But I don't see why that would interfere with extensions installed by policy. A basic design principal of enterprise policy is WebDriver should never be allowed to circumvent policies.
Status: Archived (was: Unconfirmed)

Sign in to add a comment