Installing WEB HTTP Sessions Driver Dependencies.

Web HTTP sessions enable secure, zero trust access to web portals. These sessions leverage a server-side web browser (Chromium) running in headless mode, with the interactive interface streamed to the proprietary web client.

Although the browser operates headlessly, it still depends on underlying graphical system libraries. Some minimal Linux distributions do not include these components by default.

In such environments, the required graphical dependencies must be installed on the host to ensure Web HTTP sessions function properly.

The required graphical dependencies can be installed at any time, even after the application has already been deployed and is running.

No application restart is necessary—Web HTTP sessions will begin functioning automatically once the dependencies are installed.

Note that all other platform capabilities will continue to operate normally without these dependencies, including credential vaulting, script execution, account management, and access via RDP, SSH, PowerShell, VNC, Telnet, and Kubernetes protocols.

Installation of Dependencies

ubuntu

Ubuntu 24+

sudo apt update && sudo apt install -y \
  libasound2t64 \
  libatk1.0-0 \
  libatk-bridge2.0-0 \
  libcups2 \
  libgbm1 \
  libgtk-3-0 \
  libnspr4 \
  libnss3 \
  libxcomposite1 \
  libxdamage1 \
  libxrandr2 \
  libxss1 \
  xdg-utils

Ubuntu pre-24

sudo apt update && sudo apt install -y \
  libnss3 \
  libatk1.0-0 \
  libatk-bridge2.0-0 \
  libxcomposite1 \
  libxdamage1 \
  libxfixes3 \
  libxrandr2 \
  libgbm1 \
  libasound2

debian

sudo apt update && sudo apt install -y \
  libnss3 \
  libatk1.0-0 \
  libatk-bridge2.0-0 \
  libxcomposite1 \
  libxdamage1 \
  libxfixes3 \
  libxrandr2 \
  libgbm1 \
  libxkbcommon0 \
  libasound2

centos

sudo dnf install -y \
  nss \
  atk \
  at-spi2-atk \
  libXcomposite \
  libXdamage \
  libXfixes \
  libXrandr \
  mesa-libgbm \
  alsa-lib

rhel

rocky

almalinux

sudo dnf install -y \
  nss \
  atk \
  at-spi2-atk \
  libXcomposite \
  libXdamage \
  libXfixes \
  libXrandr \
  mesa-libgbm \
  libxkbcommon \
  alsa-lib

fedora

sudo dnf install -y \
  nss \
  atk \
  at-spi2-atk \
  libXcomposite \
  libXdamage \
  libXfixes \
  libXrandr \
  mesa-libgbm \
  alsa-lib

oracle

ol

sudo dnf install -y \
  nss \
  atk \
  at-spi2-atk \
  libXcomposite \
  libXdamage \
  libXfixes \
  libXrandr \
  mesa-libgbm \
  alsa-lib

alpine

sudo apk add --no-cache \
  nss \
  atk \
  at-spi2-atk \
  libxcomposite \
  libxdamage \
  libxfixes \
  libxrandr \
  mesa-gbm \
  alsa-lib

Verification of correct deployment.

To verify that the graphical components are properly installed and the Web HTTP driver is functioning correctly, navigate to the application’s installation directory and execute the following command.

The command should return the version of the Web HTTP driver, confirming that the environment is correctly configured.

./wd/chrome-headless-shell --headless --version

To further confirm that the driver can be successfully initialized, run the following command to start it in operational mode.

If the driver launches without errors, it indicates that the environment is correctly configured and ready for use.

./wd/chrome-headless-shell --headless --remote-debugging-port=9022

If the driver fails to start, review the error messages displayed in the console. They will indicate any missing dependencies or configuration issues, such as the inability to bind to the specified port.

Resolve the reported issues and re-run the command to confirm proper operation.