Read this article if you do not have your custom build of the screen-sharing extension, yet.
1. Register for a Firefox add-ons account
Register at: https://addons.mozilla.org
This step will allow you to create your own API key and secret for extension signing.
2. Generate the API key
If you have an existing credential, skip this step.
Under Tools > Manage API Keys, Click on the Generate new credential button. These generated credentials can then be used for signing the extension.
3. Sign the extension
Refer to documentation from Mozilla here, to learn how to sign your extension if you are not hosting it on Mozilla Add-ons (AMO).
How signing works
Extensions that are submitted for hosting on AMO and pass review, will be automatically signed. Extension files that aren’t hosted on AMO will have to be submitted to AMO for signing. Developers will need to create accounts and a listing for their extension, which will not be public. These files will go through an automated review process and sent back signed, if all checks pass.
Using an unsigned extension
It will not be possible to install unsigned extensions in the current versions Firefox. There won’t be any preferences or command line options to disable this. Installation of unsigned extensions will still be possible on Nightly and Developer Edition, as well as special, unbranded builds of Release and Beta that will be available mainly for developers testing their extensions.
4. Modify the AdapterJS to point to your Firefox extension to download
To use your custom extension, you will need to customise AdapterJS to point to your extension.
Learn how to load your custom AdapterJS here.
After configuring AdapterJS, replace the URL specified between the << >> tags, as shown below in the adapter.screenshare.js file under the publish folder, to point to the link of your customised extension:
AdapterJS.renderNotificationBar(AdapterJS.TEXT.EXTENSION.REQUIRE_INSTALLATION_FF, AdapterJS.TEXT.EXTENSION.BUTTON_FF, '<<http://skylink.io/screensharing/ff_addon.php?domain=' + window.location.hostname>>', false, true);