UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. The user wants to share their desktop with others on a WebRTC conference site.
2. The site admin must create and distribute an extension to whitelist the domain which the user must then install to enable desktop sharing with Chrome(ium).

What is the expected behavior?
It would be more intuitive if the user approved each site for desktop sharing through a UI popup, as done with Video or Audio permissions:

[site] wants to 
* Use your microphone
* Use your camera
[Block][Allow]

This is also the current Firefox behavior for WebRTC desktop sharing. Another option is just to have a whitelist preference the user/admin can set themselves.

What went wrong?
If an organization wants to run a private Jitsi Meet (or other WebRTC) server behind the corporate firewall, the admin must have every user install a custom extension to enable screen sharing. However, modern versions of Chrome automatically remove extensions not installed through the Chrome Web Store, resulting in a situation where the admin must upload an extension to the Chrome Web Store whitelisting their domain. This is a very cumbersome process to essentially set a preference.

Did this work before? No 

Chrome version: 66.0.3359.139  Channel: n/a
OS Version: 
Flash Version: 

The current Jitsi Meet solution is to modify https://github.com/jitsi/jidesha with the proper domain and upload the extension to the Web Store or otherwise distribute.

"""
Create the extension
Edit the manifest.json file. You must adapt the externally_connectable URL:

"matches": [
    "*://your.server.com/*"
]
"""