Advanced configuration and custom integration options
Apache Guacamole is configured using files within the
/etc/guacamoledirectory, commonly referred to as
GUACAMOLE_HOME. The two primary components of the Apache Guacamole stack, guacd and the Guacamole web application, both have their own dedicated configuration files within
/etc/guacamole. Keeper Connection Manager includes default, skeleton versions of these files.
Supported extensions, such as those provided by the Keeper Connection Manager packages, are installed through installing their corresponding packages. If you are using the keeper/guacamole Docker image, extensions are automatically installed using the above packages depending on the environment variables provided when the container is first started.
The Keeper Connection Manager packages for supported extensions will automatically create symbolic links to install themselves and any needed libraries/drivers. You do not need to manually create links, copy files, etc. for the extensions which are provided within the Keeper Connection Manager repository.
Custom extensions, such as custom branding provided as part of a Keeper Connection Manager subscription, are installed by placing their corresponding .jar files within
/etc/guacamole/extensions. If those extensions require additional libraries, such as JDBC drivers, the .jar files for those libraries are placed within
Note that support is not provided for custom extensions with the following exceptions:
Custom branding is applied through branding extensions, such as the branding extensions we provide on request as part of a Keeper Connection Manager subscription. If you have a custom branding extension and wish to apply that branding to your deployment of Keeper Connection Manager, you must:
- 1.Remove the symbolic link to the default Keeper Connection Manager branding, located at
kcm-guacamolepackage considers the existence/absence of this link to be an aspect of configuration and is designed to allow this symbolic link to be removed. If using the keeper/guacamole Docker image, this can also be accomplished by setting the
USE_DEFAULT_BRANDINGenvironment variable to "N".
- 2.Copy the extension's .jar file to
- 3.Restart Tomcat
You may need to clear cache within browsers that have already visited your deployment.