Skip to content

VNC

VNC is another way to view and control a machine’s graphical screen, common on Linux desktops, Macs, and appliances that expose a VNC server. Through the Bridge, users reach those screens with the session policy-controlled and recorded.

VNC is browser-only. There is no native VNC listener - users always connect through the Bridge web interface, and the remote screen is rendered in-browser. There is nothing to install and no port to configure.

Granting access. Settings here enable VNC for the deployment. To grant a person access to a host, create a checkout - VNC uses a backend password and the copy/paste toggles in the RDP options.

Browser mode

Turn on browser mode to make VNC checkouts available in the web interface.

bridge.yaml
vnc:
  browser:
    enabled: true

That is the only switch VNC needs. When enabled, users with a VNC checkout open the remote desktop directly in their browser.

Display options and clipboard sharing are granted per checkout as part of the access policy, not in this configuration file.

Example

bridge.yaml
vnc:
  browser:
    enabled: true

VNC has no idle timeout setting. Every other protocol has one, so if you need VNC sessions to close on inactivity, say so: nothing in the configuration file does it today.

Option reference

OptionTypeDefaultDescription
vnc.browser.enabledboolfalseTurn on the in-browser VNC remote desktop.
Last updated on