If enabled, the access will be proxied through the Nodegrid device, with two possible scenarios:

a) If Internal Browser is selected, Nodegrid internally opens a browser and shows/streams it to the user.

b) If Browser Forwarder is selected, the device’s WEB or KVM session is opened directly on the user’s browser, but all the communication is proxied through Nodegrid (the device doesn’t need to be in the same network as the user). This option typically shows better connection latency, but has stricter requirements (see below) and is not guaranteed to work with every managed device.
The following managed devices have been validated by ZPE to be compatible with this option: Console Server ACS, Edgecore Switch, PDU CPI, Raritan DSX2, Raritan DKX3, Raritan DKX4, Raritan PX3, Servertech PRO4X, Fortinet FortiGate

The following managed devices are compatible for Web sessions, but not for KVM sessions: Avocent MPU, iDRAC 8, iDRAC 9, iLO 4, iLO 5.

Devices not listed above may or may not be fully compatible with this option.
This option has the following requirements. If they are not met, the connection will automatically fallback to the Internal Browser method:

1. Limited to Chromium-based browsers (e.g. Google Chrome, Microsoft Edge),

2. When accessing through ZPE Cloud, for some managed devices, the URL for the managed device (e.g. as configured in “WEB URL” field) must start with “https://”,

3. An HTTPS connection from the user’s browser to the Nodegrid with a certificate trusted by the browser can be established. This can be achieved with one of the following options:

   1. The Nodegrid is accessed through ZPE Cloud, or

   2. The Nodegrid device uses a certificate signed by a certification authority trusted by the browser, or

   3. The certificate installed in the Nodegrid device is installed in the browser

      Refer to the section Certificates Tab and the article Install a X.509 Certificate from a Certificate Signing Request for more information about trusted certificate environments.