How to enable an extension not hosted on Google Play store?

[Mike Moore]

McAfee SiteAdvisor Enterprise (SAE) is a third party installed extension that no longer is enabled in Chrome 35 and higher. 

SAE is currently a NPAPI based extension. McAfee is working on a non NPAPI extension. In the interim, I am trying to work out how to get the current SAE extension enabled in Chrome.

After checking in the Chrome ADM into Windows group policy editor, I tried to configure 2 settings to get SAE to be enabled.

Default domain policy > Computer configuration > Administrative templates > Google > Google Chrome > Extensions

Configure list of force installed extensions

                Feobgjncdknhelkhjpiejdbpliekmfaj;http://beaqaftp.beaqa.lab/mcafeesiteadvisorcrx/updates.xml

Configure extension, app and user script install sources

                http://beaqaftp.beaqa.lab/*

Here is the contents of the updates.xml file.

<?xml version='1.0' encoding='UTF-8'?>

<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>

<app appid='feobgjncdknhelkhjpiejdbpliekmfaj'>

    <updatecheck codebase='http://beaqaftp.beaqa.lab/McAfeeSiteAdvisorCRX/McChPlg.crx' version='3.5.0.1204' />

</app>

</gupdate>

 

Updates.xml and mcchplg.crx are hosted on this web server. http://beaqaftp.beaqa.lab/McAfeeSiteAdvisorCRX/

The manifest.json in the mcchplg.crx is version 3.5.0.1204.

The SAE ID in Chrome is feobgjncdknhelkhjpiejdbpliekmfaj.

 

This did not allow SAE extension to load. Any ideas on how to get the SAE extension working in Chrome 35 and higher?

[Rajesh Katalkar]

The GPO style only works in domain enterprise environment AFAIK.There is no temporary solution as this was warned long time back.

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/15786a2e-ec3f-4300-882d-7de1074d9bf3%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Mike Moore]

It is not working in a domain environment.

On Saturday, August 30, 2014 7:55:10 AM UTC-7, Rajesh Katalkar wrote:

The GPO style only works in domain enterprise environment AFAIK.There is no temporary solution as this was warned long time back.

On Fri, Aug 29, 2014 at 5:01 AM, Mike Moore <siteadvis...@gmail.com> wrote:

McAfee SiteAdvisor Enterprise (SAE) is a third party installed extension that no longer is enabled in Chrome 35 and higher. 

SAE is currently a NPAPI based extension. McAfee is working on a non NPAPI extension. In the interim, I am trying to work out how to get the current SAE extension enabled in Chrome.

After checking in the Chrome ADM into Windows group policy editor, I tried to configure 2 settings to get SAE to be enabled.

Default domain policy > Computer configuration > Administrative templates > Google > Google Chrome > Extensions

Configure list of force installed extensions

                Feobgjncdknhelkhjpiejdbpliekmfaj;http://beaqaftp.beaqa.lab/mcafeesiteadvisorcrx/updates.xml

Configure extension, app and user script install sources

                http://beaqaftp.beaqa.lab/*

Here is the contents of the updates.xml file.

<?xml version='1.0' encoding='UTF-8'?>

<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>

<app appid='feobgjncdknhelkhjpiejdbpliekmfaj'>

    <updatecheck codebase='http://beaqaftp.beaqa.lab/McAfeeSiteAdvisorCRX/McChPlg.crx' version='3.5.0.1204' />

</app>

</gupdate>

 

Updates.xml and mcchplg.crx are hosted on this web server. http://beaqaftp.beaqa.lab/McAfeeSiteAdvisorCRX/

The manifest.json in the mcchplg.crx is version 3.5.0.1204.

The SAE ID in Chrome is feobgjncdknhelkhjpiejdbpliekmfaj.

 

This did not allow SAE extension to load. Any ideas on how to get the SAE extension working in Chrome 35 and higher?

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

[joaod...@chromium.org]

Hi Mike,

this thread has just been brought to my attention. I'm happy to help if you're still having issues.

First, can you load the extension directly from chrome://extensions as an unpacked extensions?

Second, is there any error reported for the ExtensionInstallForcelist policy in chrome://policy when you have those settings in GPO?

The update.xml file you've posted looks correct so this should work. The NPAPI is still working even in Chrome 37. The only details I've noticed is that the extension ID is capitalized in the policy value (it must be all lowercase), and the update URL is all lowercase but in the updates.xml file it has some capitalization in the path.

I can try to set this up locally and see if I find any problems if you mail me the CRX privately.

Let me know if this help.
Thanks,
- Joao

[Mike Moore]

I cannot get SAE extension to load. I get message stating "McAfee SiteAdvisor Enterprise (extension ID "feobgjncdknhelkhjpiejdbpliekmfaj") is  blocked by administrator".

Here is what chrome://policy shows. 

Applies to	Level	Policy name	Policy value	Status
Machine	Mandatory	ExtensionInstallForcelist	Hide value	OK
feobgjncdknhelkhjpiejdbpliekmfaj;http://beaqaftp.beaqa.lab/mcafeesiteadvisorcrx/updates.xml
Machine	Mandatory	ExtensionInstallSources	Hide value	OK
http://beaqaftp.beaqa.lab/*,http://beaqaftp.beaqa.lab/mcafeesiteadvisorcrx/*

 

[Joao da Silva]

That looks correct and should have worked. Note that the ExtensionInstallSources policy is not necessary to allow installs via the forcelist.

Do you think you can mail me that CRX and the updates.xml file privately? I'd be happy to try to reproduce this locally and investigate further.