Private hosting (Chrome)

Deploy the JNLP Runner chrome extension via Group Policy (Windows).

If your organisation requires to use our extension in multiple devices, we have amazing news for you! Our JNLP Runner extension is available for private hosting and deployment via Group Policy. This way, you can deploy our extension for multiple users under your organisation simultaneously and administrate it from a single place. This page will take you step by step on how to do this.


  • The appropriate IT permissions at your organisation.
  • The JNLP Runner extension CRX file.

The CRX File and DownloadURL

The CRX file is a compressed format for extensions of browsers belonging to the Chromium family (such as Google Chrome). To obtain the CRX file of the JNLP runner extension for self-hosting, you will need to contact us and we will be happy to provide it for you alongside a license token.

Host the extension CRX file in an appropriate location in your IT infrastructure and create a download URL to access it. You will need this URL later in the tutorial.

About DownloadURL
You can also use the WebStore’s DownloadURL, but you won’t be self-hosting the extension and it will be retrieved from the WebStore for all your users. This is a limitation for IT infrastructures where the organisation devices do not have connection permissions to the wider internet. For this reason we recommend the self-hosting method.

The extension ID

The extension ID is a unique identifier used by the Chrome WebStore. You can retrieve from the extension Chrome Web Store URL (last 32 characters):

The extension ID is:


The policy string

Now that you have the extension’s CRX file and ID, you can build the policy string by merging the extension’s ID and the CRX DownloadURL separated by a semicolon: ID;DownloadURL It must look something like this: achnhggjjhnadfapkmgallnbmemdojdi;

Hypothetical URL
The example above contains hypothetical URL, please do not use this policy string.

Policy templates

You will need to download and install the Google administrative templates. You can do this by downloading the templates file and following the steps as stated in the Chrome policies guide by Google.

Chrome policies

Creating a new group policy

Now you have everything you need to create a new GPO, please follow these final steps to create a Group Policy or you can edit an existing one:

  1. Open the Group Policy Management interface
  2. Go to your desired domain and right click to display the options menu.
  3. Click on Create a GPO in this domain, and Link it here…
  4. Name your policy object and hit Ok.
  5. Right click on top of the policy object you just created and click Edit.
  6. On the left menu, find the folder Administrative Templates: Policy definitions > Google > Google Chrome > Extensions.
  7. On the right side of the window, click on Configure the list of force-installed apps and extensions. This will display a new window with the same title.
  8. Click in the radio button Enabled and then click on the button Show…, this will prompt a small window named Show Contents.
  9. Now copy the policy string ID;DownloadURL you created in the previous step and paste it under the cell Value, click Ok and apply the changes.

Licensing and further group policy setup

The final step is to setup your license among other relevant configurations for this Group Policy.

  1. Open the Group Policy Management interface, find the JNLP Runner group policy you created previously and click Edit.
  2. On the left menu, find Administrative Templates: Policy definitions > Google > Google Chrome > Extensions.
  3. On the right side menu click on Configure Extension management settings.

In this window you can configure all the settings relevant for your organisation when using the JNLP runner extension. To do so you need to input the relevant settings in JSON format into the editor. This is done by editing the JSON string shown in the interface using the format:

{ "*": { "FieldKey": "FieldValue" } }

The Key (*) will apply the settings to all extensions or apps under this policy. Remember to use the extension ID for those settings that you want to apply only for the JNLP Runner extension.

{ "ExtensionIDHere": { "SettingField": "FieldValues" } }


To correctly configure your license, make sure to include the license token field in your JSON:

{ "ExtensionIDHere": { "licenseToken": "YourValidTokenHere" } }

Other settings

Remember you can always configure other settings for this Group Policy that are appropriate for your group of users and the extension. You can do this in this same JSON adding the appropriate key/values as the examples shown below:

For example:

  • Always pin this extension to the browser toolbar
{ "ExtensionIDHere": { "toolbar_pin": "force_pinned" } }
  • Pre-allow specific permissions for the extension (see permissions list). For example, to perform downloads:
{ "ExtensionIDHere": { "allowed_permissions": ["downloads"] } }
  • Block extension from interacting with certain websites:

    { "runtime_blocked_hosts": ["*://"] }
  • Allow the extension to interact with specific websites even when they’re in the blocked list:

{ "runtime_allowed_hosts": ["*://"] }

For more information about extension settings visit The Chrome Documentation

Chrome Documentation

Update your changes

Once you are happy with your group policy configuration, you can apply these changes to see them reflected on your user’s chrome clients by running the shell command:

Terminal window

Now your users should be able to see the extension installed in their Chrome browser.

Was this page helpful?
Suggest changes