Lably
Skip to content

Apache Guacamole

  • 2 min read
  • 3 chapters

Related on Lably

Through Free and open-source software, Virtual machine and Web browser

Remote access is performed via the guacd component, which uses the RDP, VNC or SSH remote protocols to access resources. Guacamole is clientless and doesn't require an agent to be installed on the resources being accessed. The fact that the client runs on web browsers allows users to connect to their remote desktops without installing a remote desktop client.

Components

Guacamole is made up of multiple components: a web application that is served to users, and a backend service ("guacd") that dynamically translates and optimizes native protocols into the Guacamole protocol. The part of Guacamole that a user interacts with is the web application.

Web Application

The web application provides the user interface, authentication, and authorization system. It does not implement any remote desktop protocol, but instead relies on guacd to translate remote desktop protocols into the Guacamole protocol. The server side of the web application is written in Java and runs beneath a servlet container like Apache Tomcat or Jetty. The client side of the web application is written in JavaScript and runs within the web browser.

guacd

guacd services requests to connect to remote desktops from the web application. It dynamically loads support for remote desktop protocols so that neither guacd nor the web application need to understand the specifics of any one remote desktop protocol. guacd and all client plugins use a shared library, libguac, to abstract away the Guacamole protocol and communication with the web application.

Sign in to keep reading

2 more chapters are free with a Lably account.

More in Everyday life