Issue 243936 in chromium: Method to verify if legacy browser support (LBS) policies are configured correctly

[chro...@googlecode.com]

Status: Unconfirmed
Owner: pasta...@chromium.org
CC: roy...@chromium.org, cyr...@chromium.org
Labels: Type-Bug Pri-2 Cr-Enterprise

New issue 243936 by danh...@chromium.org: Method to verify if legacy
browser support (LBS) policies are configured correctly
http://code.google.com/p/chromium/issues/detail?id=243936

Version of Google Chrome (Wrench-> About Google Chrome): 27.0.1453.94
Using group policy settings? Yes

Looking for a way to confirm if LBS configuration policies are being
correctly applied to the browser, similar to how one can
check 'chrome://policy' for enforced browser settings. Have a customer
experiencing an issue with the Chrome->IE transition though going from
IE->Chrome works fine.



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Assigned

Comment #1 on issue 243936 by pasta...@chromium.org: Method to verify if

legacy browser support (LBS) policies are configured correctly
http://code.google.com/p/chromium/issues/detail?id=243936

Joao, who is also CCed on this bug can give you estimate about when will
extension policy be shown on the about:policy page. Until then the only
indicator you have if this is applied is whether or not the extension
works :)

However from what you say the extension has to have policy since it is
responsible for caching and providing the policy to the IE Add-on as well
and you claim this part works well.

Can you please ask the customer to describe what doesn't work in the other
direction Chrome->IE? Also ask for the policy contents as configured if
possible (anonymized is fine as long as the exact format of the entries is
preserved).

[chro...@googlecode.com]

Comment #3 on issue 243936 by pasta...@chromium.org: Method to verify if

legacy browser support (LBS) policies are configured correctly
http://code.google.com/p/chromium/issues/detail?id=243936

The policy seems well configured. I can think of two things that could
inhibit the Chrome extension from operating:

1. If you have a policy to disable plugins make sure you have enabled the
Legacy Browser Support plugin which is bundled with the extension. You can
verify this on the http://about:plugins page.

2. Make sure the Alternative Browser Path policy is pointing to a valid
executable. If you don't want to specify this you can either leave it not
set or use the "${ie}" value without the quotes to let the extension try to
detect where IE is installed. To verify that this is not the problem you
can specify a dummy but guaranteed to exist executable here like
notepad.exe or something similar and check if it gets called when one of
the urls is used.

If none of the above helps you can check the log file
in %USERPROFILE%\AppData\Local\Google\BrowserSwitcher\plugin_log.log if it
contains any errors.

One tip in the end that can improve the performance of your set-up: You
don't have to specify both domains and sub-domains since the matching is
done on the host contains principle which means that if you
have "example.com" as an entry this will cover both example.com as well as
foo.example.com.

[chro...@googlecode.com]

Comment #4 on issue 243936 by pasta...@chromium.org: Method to verify if

legacy browser support (LBS) policies are configured correctly
http://code.google.com/p/chromium/issues/detail?id=243936

Now that I think more about it - the plugin can't be blocked because it is
delivering the cache file for the IE add-on. Now the only reason that is
left is that Chrome can't start IE for some reason so I'd suggest you
concentrate on the Alternative Browser Path policy and make sure it is
valid.

Also are there any red warnings below the extension on the about:extensions
page? You need at least Chrome 26 for this extension to work properly.

[chro...@googlecode.com]

Updates:
Blockedon: chromium:248533

Comment #5 on issue 243936 by joaod...@chromium.org: Method to verify if

legacy browser support (LBS) policies are configured correctly
http://code.google.com/p/chromium/issues/detail?id=243936

This bug can be closed once policy-for-extensions is displayed in
chrome://policy (issue 248533).