Testing Basic Functionality with "user-mapping.xml"
Apache Guacamole comes with a built-in, simplified, XML-driven authentication mechanism for the sake of testing. Accounts and connections can be defined within /etc/guacamole/user-mapping.xml without having to install support for a database. The default file included with Keeper Connection Manager looks like this:
As noted at the top of the file, you can leverage this to verify that your Guacamole installation is functional, however the user-mapping.xml file should not be used for production deployments. Production deployments of Guacamole should instead use one of the authentication extensions, such as the database support or LDAP. Unlike the XML, all of these extensions are intended for production use.
user-mapping.xmlThe user-mapping.xml file consists of a main, root-level <user-mapping> element:
This <user-mapping> element may contain any number of <authorize> blocks, each describing a user and their corresponding password:
The <authorize> blocks in turn may contain any number of <connection> blocks, each describing a connection that should be accessible to the user:
This file is automatically reread when modified, so you should be able to immediately log in when you define a new user in this way, however changes to an active user’s connections will not be available to that user until they logout.
When finished testing, you should prepare to move forward with adding the remaining layers normally required by a production deployment: