/etc/guacamole/user-mapping.xml
without having to install support for a database. The default file included with Keeper Connection Manager looks like this: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.xml
user-mapping.xml
file consists of a main, root-level <user-mapping>
element:<user-mapping>
element may contain any number of <authorize>
blocks, each describing a user and their corresponding password:<authorize>
blocks in turn may contain any number of <connection>
blocks, each describing a connection that should be accessible to the user:<connection>
contains exactly one <protocol>
element (specifying the unique name of the protocol to use to connect to the remote desktop) and any number of <param>
elements (specifying the name of a parameter and the value to use for that connection). These protocol and parameter names are standardized and case-sensitive. The names of each supported protocol are defined by Guacamole, and the names of available parameters are defined by the part of Guacamole implementing that support:user-mapping.xml
, encrypted JSON, connections defined directly within an LDAP directory, or custom extensions leveraging the Guacamole API). They are not visible when using one of the database authentication backends except if manually manipulating data within the database using SQL.