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

Issue 767860 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Dynamic Policy Refresh is not working for ExtensionInstallSources and ExtensionInstallWhitelist

Reported by parthivs...@gmail.com, Sep 22 2017

Issue description

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

Steps to reproduce the problem:
1. Create registry entries for ExtensionInstallSources and ExtensionInstallWhitelist while chrome is running.
2. Try to install extension hosted on server.
3. Observe extension is not installed as policies are not loaded.
4. Observe chrome://policy does not define Policy.

What is the expected behavior?
Policies should be loaded dynamically while chrome is running. User should be able to install extension.

What went wrong?
Policies which are added using registry entries are not loaded dynamically. If I go to chrome://policy and click on Reload Policy button, it fetches the policies. and I am able to install extension.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: 

I have attached screenshots of before Reloading Policy and after Reloading Policy. Let me know if there is a way to reload policy programatically.
 
Capture0.PNG
25.3 KB View Download
Capture1.PNG
25.6 KB View Download
Capture2.PNG
20.1 KB View Download
Cc: georgesak@chromium.org blumberg@chromium.org pastarmovj@chromium.org
Labels: Enterprise-Triaged
Status: Available (was: Unconfirmed)
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 24

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: goanuj@chromium.org
Status: Assigned (was: Untriaged)
Cc: -blumberg@chromium.org jawag@chromium.org rdevlin....@chromium.org

Sign in to add a comment