Deploying Connect Extensions in Closed Environments
Locked-down or enterprise environments without access to the public internet generally require special steps to acquire and enable Connect web extensions. Depending on OS platform and browser, there are a number of methods for doing so.
Chrome
Method: Manual deployment Using Drag and Drop
Firefox
Method: Manual deployment
Method: Deploying Aspera Connect add-on with custom build of Firefox
See Mozilla documentation:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Distribution_options/Add-ons_in_the_enterprise#Bundling_add-ons_with_a_custom_Firefox
Whitelisting the Chrome Extension
By default, all Chrome extensions are whitelisted. However, if your organization blacklists all extensions by policy, you can override the blacklist and allow the Connect extension to be installed by adding it to the whitelist.
https://www.chromium.org/administrators/policy-list-3#ExtensionInstallWhitelist
The instructional links below also include information on other extension-related policy settings that enable you to automatically install Chrome, force-install Chrome, and so on.
Provisioning Policy Using Chrome Policy Templates