# Browser extension installation guide

The browser extension Sirenia Web Automation Driver facilitates automation and context management in modern browsers. It is available for chrome, firefox and edge and extension compatible variations of these browsers.

This document contains instructions on how to install the extension as an end-user as well as links to resources on centralized rollout.

For larger organizations who need automation to be readily available to a large number of users, centralized rollout is generally preferable. This can be done with Microsoft Active Directory through a suitable Group Policy Object (GPO).

WARNING

The extension relies on the browser feature native host messaging, so make sure not to disallow that.

# Chrome

The chrome extension lives in the Chrome store.

# End user

The end user may simply point Chrome to the above location and click ‘Add to Chrome’.

# Centralized rollout

Google documents the process here. The extension id needed for the GPO is lbokehfhhclmidfioacglfeigplbccdj.

Sample GPO json:

{
  "lbokehfhhclmidfioacglfeigplbccdj": {
    "installation_mode": "force_installed",
      "update_url":
      "https://clients2.google.com/service/update2/crx"
  }
}

In compact form:

{"lbokehfhhclmidfioacglfeigplbccdj":{"installation_mode": "force_installed","update_url":"https://clients2.google.com/service/update2/crx"}}

# Edge

Due to the similarities between the chromium based Edge browser and Chrome, both the Chrome extension and the Edge extension are compatible with Edge. The native Edge extension can be found on the Microsoft store.

# End user

The end user may simply point Edge to the above location and click Get to install it.

# Centralized rollout

Microsoft document the procedure here. The extension id needed for the procedure is kjnjgmmokhgfibgjcidmnhkjmcnnccdm.

WARNING

Beware that ‘Microsoft Security Compliance Toolkit’ defaults to disabling the native host messaging feature which is required by this extension.

# User level messaging host

The way the native messaging manifest is currently registered in the Windows registry (under the HKCU cluster) means that user level messaging hosts must be allowed.

If this is not an option, it is possible to deploy an alternative messaging manifest such as the following to a write-protected network share accessible to all users - or alternatively deployed to a write-protected area on all end user machines:

{
  "name": "eu.sirenia.manateediscoverer",
  "description": "ManateeDiscoverer",
  "path": "C:\\Program Files (x86)\\Sirenia\\Manatee\\Tools\\NativeHost\\Discoverer\\ManateeDiscoverer.exe",
  "type": "stdio",
  "allowed_origins": [
    "chrome-extension://lgipdhpkffanmmbajpbiphmklhdplmen/",
    "chrome-extension://kjnjgmmokhgfibgjcidmnhkjmcnnccdm/"
  ]
}

To put the manifest to use, it must be pointed to from the windows registry key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\eu.sirenia.manateediscoverer. The (Default) entry under that key should have as its value the path to the above manifest file.

With such a setup, Edge should allow the native host messaging to take place.

# Firefox

We publish our firefox extension to this page.

# End user

The end user may simply point Firefox to the above location and click Click here to install.

# Centralized rollout

Mozilla resources on this subject can be found here.

The process requires the following location of the extension .xpi file: https://firefox.sirenia.io/sirenia_web_automation_driver.xpi.