Auto enable chrome extension installation - google-chrome

I am using Chrome 25.0.1364.152 m and I develop a Chrome Extension. I wanna install it as an external extension and I succeed. The only problem is that I must enable this extension manually. That means I have to enable it every user profile. (I have lots of Chrome user profile on my machine) Is there any way to do this enable work automatically(via preference or something)?

Related

Local Mac OS Chrome Policy

I have few locally build extensions which I want to be force installed in my browser. So they should not have option to disable them.
Is it possible to get it without Google Admin. Locally or somewhere. Possibly I should use Chromium or even Brave browser.
I tried edit ~/Library/Preferences/com.google.Chrome.plist but it does not install extensions even from store.

Enable an enterprise deployed extension from the chrome store without prompting the user

I need to install a Chrome extension from the Chrome store to the managed workstations on my network in such a way that users (or at least users with administrator privileges) can temporarily reinstall it if necessary to troubleshoot issues.
I have tried the Force-installed extensions setting in Group Policy, but this prevents disabling or removing the deployed extensions. Instead, I tried Chrome Extension policies (https://support.google.com/chrome/a/answer/7532015), but with this method the extension is disabled by default due to Chrome security policies, requiring the user to manually approve it.
I realize that this is expected behavior to prevent application developers from auto-enabling a malicious or unwanted extension without the user's knowledge, but I am an enterprise admin trying to deploy a sanctioned extension to my managed machines.
How can I deploy and automatically enable an enterprise-installed extension without user interaction on my managed workstations, but allow that extension to be temporarily uninstalled?

How to enable chrome extension without user intervention (programmatically)

I made a chrome extension and want its installation to be done as a part of software installation setup using windows registry. It installs the extension for chrome, but in disabled state. Extension is listed in the list of installed extension in chrome://extensions. How can I enable the extension using code(without end-user intervention). I don't want my user to enable it manually.
You can't directly enable chrome extension because of chrome security police(After Chrome 25).
Extensions installed by third party programs using external extension deployment options will be disabled by default. When a third party program installs an extension, the Chrome menu will be badged, and users can click through the Chrome menu to see a dialog containing an option to enable the extension or to remove it from their computer.
In addition, all extensions previously installed using external deployment options will be automatically disabled. Chrome will show a one-time prompt to allow the re-enabling of any of the extensions.
But you can use inline installation but you need to upload your extension in Chrome Web Store and ask to user directly like this.
For More information check below links :
No more silent extension installs
Protecting Windows users from malicious extensions

install chrome extension outside the chrome extension market

As I know you can install an extension outside the market without expected limitations, for example, autoupdate. You need to be in develop mode.
You can read this thread to understand the problem:
Install chrome extension as external extensions
The think is, anyone know another way to install an extension in your chrome (internal use in a company o class). I like to think that I can sign the extension with a shared certificate or something like that. And send the extension to the users.
Google no longer allows it.
Protecting Chrome users from malicious extensions
Continuing to protect Chrome users from malicious extensions
There are 4 types of extension install still available:
Direct installation from Webstore or inline install from a website, but hosted on Web Store.
Indirect installation through registry manipulation (e.g. companion extension for a native app), but it still must be hosted in the Webstore.
Local development installs; will nag on every Chrome restart and no autoupdate mechanism.
For Enterprise only, policy-based installs. Note that on Windows that requires computers joined to a domain. In this case there are no restrictions on where the extension is hosted.

Installing External Extension

I want to create a Chrome extension and install it as part of a larger desktop software install. This is on Windows XP/Vista/7 etc. I've used the method described here and it works.
However, the extension is installed in a disabled state. The user has to explicitly enable it from the Chrome menu (the user has 3 chances to do that before the menu badge disappears) or from the extensions page. Enabling the extension brings up a prompt in which Chrome informs the user of the permissions the extension is requesting and asks the user to reject or accept the extension.
I understand that Google wants to ensure that users have a chance to reject external extensions. I also understand that Google prefers installs via its Web Store (for various logistical reasons, that is not a preferred option for this app). In fact, our application specifically asks the user for permission before installing the extension.
My issue is that the member has to affirmatively ask for the extension to be enabled before the permissions dialog comes up. Is there any programmatic/command line way to get Chrome to bring the permissions dialog up? The user still has the choice of rejecting the extension, but I would like to present the user with this choice, rather than relying on him/her to try and enable the extension later.
[ I realize that editing the Chrome Preferences file in the installation script will install the extension without any user intervention, but I don't want to do that.]
It's possible to trigger an install from a webpage. Have your installer open chrome with a small webpage that brings up this dialog to the user.