Table of Contents
Guacamole supports LDAP authentication via an extension available from the main project website. This extension allows users and connections to be stored directly within an LDAP directory. If you have a centralized authentication system that uses LDAP, Guacamole's LDAP support can be a good way to allow your users to use their existing usernames and passwords to log into Guacamole.
To use the LDAP authentication extension, you will need:
An LDAP directory as storage for all authentication data, such as OpenLDAP.
The ability to modify the schema of your LDAP directory.
The instructions here assume you already have an LDAP directory installed and working, and do not cover the initial setup of such a directory.
Important
This chapter involves modifying the contents of GUACAMOLE_HOME -
the Guacamole configuration directory. If you are unsure where
GUACAMOLE_HOME is located on your system, please consult Chapter 5, Configuring Guacamole before proceeding.
If the LDAP extension is installed, Guacamole will authenticate users against your LDAP server by attempting a bind as that user. The given username and password will be submitted to the LDAP server during the bind attempt.
If the bind attempt is successful, the set of available Guacamole connections is
queried from the LDAP directory by executing an LDAP query as the bound user. Each
Guacamole connection is represented within the directory as a special type of group:
guacConfigGroup. Attributes associated with the group define
the protocol and parameters of the connection, and users are allowed access to the
connection only if they are associated with that group.
This architecture has a number of benefits:
Your users can use their existing usernames and passwords to log into Guacamole.
You can manage Guacamole connections using the same tool that you already use to manage your LDAP directory, such as Apache Directory Studio.
Existing security restrictions can limit visibility/accessibility of Guacamole connections.
Access to connections can easily be granted and revoked, as each connection is represented by a group.
Important
Though Guacamole connections can be stored within the LDAP directory, this is not required. Connection data can alternatively be stored within a database like MySQL or PostgreSQL as long as the LDAP username matches the username of the database user. Configuring Guacamole to use a database for authentication or connection storage is covered in Chapter 6, Database authentication and later in this chapter in the section called “Associating LDAP with a database”.
The LDAP authentication extension is available separately from the main
guacamole.war. The link for this and all other
officially-supported and compatible extensions for a particular version of Guacamole are
provided on the release notes for that version. You can find the release notes for
current versions of Guacamole here: http://guacamole.incubator.apache.org/releases/.
The LDAP authentication extension is packaged as a .tar.gz file
containing:
guacamole-auth-ldap-0.9.13-incubating.jarThe Guacamole LDAP support extension itself, which must be placed in
GUACAMOLE_HOME/extensions.schema/LDAP schema files. An
.ldiffile compatible with OpenLDAP is provided, as well as a.schemafile compliant with RFC-2252. The.schemafile can be transformed into the.ldiffile automatically.
Although your LDAP directory already provides a means of storing and authenticating users, Guacamole also needs storage of connection configuration data, such as hostnames and ports, and a means of associating users with connections that they should have access to. You can do this either through modifying the LDAP directory schema, or through using a database like MySQL or PostgreSQL. If you do not wish to use the LDAP directory for connection storage, skip ahead to the section called “Associating LDAP with a database”.
If you wish to store connection data directly within the LDAP directory, the required
modifications to the LDAP schema are made through applying one of the provided schema
files. These schema files define an additional object class,
guacConfigGroup, which contains all configuration information
for a particular connection, and can be associated with arbitrarily-many users and
groups. Each connection defined by a guacConfigGroup will be
accessible only by users who are members of that group (specified with the
member attribute), or who are members of associated groups
(specified with the seeAlso attribute).
Important
The instructions given for applying the Guacamole LDAP schema changes are specific to OpenLDAP, but other LDAP implementations, including Active Directory, will have their own methods for updating the schema.
If you are not using OpenLDAP, a standards-compliant schema file is provided that can be used to update the schema of any LDAP directory supporting RFC-2252. Please consult the documentation of your LDAP directory to determine how such schema changes can be applied.
The schema files are located within the schema/ directory of the
archive containing the LDAP extension. You will only need one of these files:
guacConfigGroup.schemaA standards-compliant file describing the schema. This file can be used with any LDAP directory compliant with RFC-2252.
guacConfigGroup.ldifAn LDIF file compatible with OpenLDAP. This file was automatically built from the provided
.schemafile for convenience.
This chapter will cover applying guacConfigGroup.ldif to an
OpenLDAP server. If you are not using OpenLDAP, your LDAP server should provide
documentation for modifying its schema. If this is the case, please consult the
documentation of your LDAP server before proceeding.
Schema changes to OpenLDAP are applied using the ldapadd
utility with the provided guacConfigGroup.ldif file:
#ldapadd -Q -Y EXTERNAL -H ldapi:/// -f schema/guacConfigGroup.ldifadding new entry "cn=guacConfigGroup,cn=schema,cn=config"#
If the guacConfigGroup object was added successfully, you
should see output as above. You can confirm the presence of the new object class
using ldapsearch:
#ldapsearch -Q -LLL -Y EXTERNAL -H ldapi:/// -b cn=schema,cn=config dndn: cn=schema,cn=config dn: cn={0}core,cn=schema,cn=config dn: cn={1}cosine,cn=schema,cn=config dn: cn={2}nis,cn=schema,cn=config dn: cn={3}inetorgperson,cn=schema,cn=config dn: cn={4}guacConfigGroup,cn=schema,cn=config#
If you install both the LDAP authentication as well as support for MySQL or PostgreSQL (following the instructions in Chapter 6, Database authentication), Guacamole will automatically attempt to authenticate against both systems whenever a user attempts to log in. That user will have access to any data associated with them via the database, as well as any visible objects within the LDAP directory. The LDAP account will be considered equivalent to the database user if the username is identical.
Data can be manually associated with LDAP users by creating corresponding user accounts within the database which each have the same usernames as valid LDAP users. As long as the username is identical, a successful login attempt against LDAP will be trusted by the database authentication, and that user's associated data will be visible.
If an administrator account (such as the default guacadmin
user provided with the database authentication) has a corresponding user in the LDAP
directory with permission to list and read other LDAP users, the Guacamole
administrative interface will include LDAP users in the overall user list presented to
the administrator, and allow connections from the database to be associated with those
users directly.
Guacamole extensions are self-contained .jar files which are
located within the GUACAMOLE_HOME/extensions directory. To install
the LDAP authentication extension, you must:
Create the
GUACAMOLE_HOME/extensionsdirectory, if it does not already exist.Copy
guacamole-auth-ldap-0.9.13-incubating.jarwithinGUACAMOLE_HOME/extensions.Configure Guacamole to use LDAP authentication, as described below.
Important
You will need to restart Guacamole by restarting your servlet container in order to complete the installation. Doing this will disconnect all active users, so be sure that it is safe to do so prior to attempting installation. If you do not configure the LDAP authentication properly, Guacamole will not start up again until the configuration is fixed.
Additional properties may be added to guacamole.properties to
describe how your LDAP directory is organized and how Guacamole should connect (and
bind) to your LDAP server. Among these properties, only the
ldap-user-base-dn property is required:
- ldap-hostname
The hostname of your LDAP server. If omitted, "localhost" will be used by default. You will need to use a different value if your LDAP server is located elsewhere.
- ldap-port
The port your LDAP server listens on. If omitted, the standard LDAP or LDAPS port will be used, depending on the encryption method specified with ldap-encryption-method (if any). Unencrypted LDAP uses the standard port of 389, while LDAPS uses port 636. Unless you manually configured your LDAP server to do otherwise, your LDAP server probably listens on port 389.
- ldap-encryption-method
The encryption mechanism that Guacamole should use when communicating with your LDAP server. Legal values are "none" for unencrypted LDAP, "ssl" for LDAP over SSL/TLS (commonly known as LDAPS), or "starttls" for STARTTLS. If omitted, encryption will not be used.
If you do use encryption when connecting to your LDAP server, you will need to ensure that its certificate chain can be verified using the certificates in Java's trust store, often referred to as
cacerts. If this is not the case, you will need to use Java's keytool utility to either add the necessary certificates or to create a new trust store containing those certificates.If you will be using your own trust store and not the default
cacerts, you will need to specify the full path to that trust store using the system property javax.net.ssl.trustStore. Note that this is a system property and not a Guacamole property; it must be specified when starting the JVM using the-Doption. Your servlet container will provide some means of specifying startup options for the JVM.- ldap-max-search-results
The maximum number of search results that can be returned by a single LDAP query. LDAP queries which exceed this maximum will fail. This property is optional. If omitted, each LDAP query will be limited to a maximum of 1000 results.
- ldap-search-bind-dn
The DN (Distinguished Name) of the user to bind as when authenticating users that are attempting to log in. If specified, Guacamole will query the LDAP directory to determine the DN of each user that logs in. If omitted, each user's DN will be derived directly using the base DN specified with ldap-user-base-dn.
- ldap-search-bind-password
The password to provide to the LDAP server when binding as ldap-search-bind-dn to authenticate other users. This property is only used if ldap-search-bind-dn is specified. If omitted, but ldap-search-bind-dn is specified, Guacamole will attempt to bind with the LDAP server without a password.
- ldap-user-base-dn
The base of the DN for all Guacamole users. This property is absolutely required in all cases. All Guacamole users must be descendents of this base DN.
If a search DN is provided (via ldap-search-bind-dn), then Guacamole users need only be somewhere within the subtree of the specified user base DN.
If a search DN is not provided, then all Guacamole users must be direct descendents of this base DN, as the base DN will be appended to the username to derive the user's DN. For example, if ldap-user-base-dn is "
ou=people,dc=example,dc=net", and ldap-username-attribute is "uid", then a person attempting to login as "user" would be mapped to the following full DN: "uid=user,ou=people,dc=example,dc=net".- ldap-username-attribute
The attribute or attributes which contain the username within all Guacamole user objects in the LDAP directory. Usually, and by default, this will simply be "uid". If your LDAP directory contains users whose usernames are dictated by different attributes, multiple attributes can be specified here, separated by commas, but beware: doing so requires that a search DN be provided with ldap-search-bind-dn.
If a search DN is not provided, then the single username attribute specified here will be used together with the user base DN to directly derive the full DN of each user. For example, if ldap-user-base-dn is "
ou=people,dc=example,dc=net", and ldap-username-attribute is "uid", then a person attempting to login as "user" would be mapped to the following full DN: "uid=user,ou=people,dc=example,dc=net".- ldap-user-search-filter
The search filter used to query the LDAP tree for users that can log into and be granted privileges in Guacamole. If this property is omitted the default of "(objectClass=*)" will be used.
- ldap-config-base-dn
The base of the DN for all Guacamole configurations. This property is optional. If omitted, the configurations of Guacamole connections will simply not be queried from the LDAP directory. If specified, this base DN will be used when querying the configurations accessible by a user once they have successfully logged in.
Each configuration is analogous to a connection. Within Guacamole's LDAP support, each configuration functions as a group, having user members (via the member attribute) and optionally group members (via the seeAlso attribute), where each member of a particular configuration group will have access to the connection defined by that configuration.
- ldap-group-base-dn
The base of the DN for all groups that may be referenced within Guacamole configurations using the standard seeAlso attribute. All groups which will be used to control access to Guacamole configurations must be descendents of this base DN. If this property is omitted, the seeAlso attribute will have no effect on Guacamole configurations.
- ldap-dereference-aliases
Controls whether or not the LDAP connection follows (dereferences) aliases as it searches the tree. Possible values for this property are "never" (the default) so that aliases will never be followed, "searching" to dereference during search operations after the base object is located, "finding" to dereference in order to locate the search base, but not during the actual search, and "always" to always dereference aliases.
Again, even if the defaults are sufficient for the other properties, you must still specify the ldap-user-base-dn property. An absolutely minimal configuration for LDAP authentication will look like the following:
# LDAP properties
ldap-user-base-dn: ou=people,dc=example,dc=netGuacamole will only reread guacamole.properties and load
newly-installed extensions during startup, so your servlet container will need to be
restarted before the LDAP authentication will take effect. Restart your servlet
container and give the new authentication a try.
Important
You only need to restart your servlet container. You do not need to restart guacd.
guacd is completely independent of the web application
and does not deal with guacamole.properties or the
authentication system in any way. Since you are already restarting the
servlet container, restarting guacd as well technically
won't hurt anything, but doing so is completely pointless.
If Guacamole does not come back online after restarting your servlet container, check the logs. Problems in the configuration of the LDAP extension will prevent Guacamole from starting up, and any such errors will be recorded in the logs of your servlet container. If properly configured, you will be able to log in as any user within the defined ldap-user-base-dn.
Guacamole's LDAP support allows users and connections to be managed purely within an
LDAP directory defined in guacamole.properties. This is
accomplished with a minimum of changes to the standard LDAP schema - all Guacamole users
are traditional LDAP users and share the same mechanism of authentication. The only new
type of object required is a representation for Guacamole connections,
guacConfigGroup, which was added to your server's schema
during the install process above.
All Guacamole users, as far as the LDAP support is concerned, are LDAP users with standard LDAP credentials. When a user signs in to Guacamole, their username and password will be used to bind to the LDAP server. If this bind operation is successful, the available connections are queried from the directory and the user is allowed in.
Each connection is represented by an instance of the
guacConfigGroup object class, an extended version of the
standard LDAP groupOfNames, which provides a protocol and set
of parameters. Only members of the guacConfigGroup will have
access to the corresponding connection.
The guacConfigGroup object class provides two new
attributes in addition to those provided by
groupOfNames:
- guacConfigProtocol
The protocol associated with the connection, such as "
vnc" or "rdp". This attribute is required for everyguacConfigGroupand can be given only once.- guacConfigParameter
The name and value of a parameter for the specified protocol. This is given as
name=valueThis attribute can be given multiple times for the same connection.
For example, to create a new VNC connection which connects to "localhost" at port
5900, while granting access to user1 and
user2, you could create an .ldif
file like the following:
dn: cn=Example Connection,ou=groups,dc=example,dc=net objectClass: guacConfigGroup objectClass: groupOfNames cn: Example Connection guacConfigProtocol: vnc guacConfigParameter: hostname=localhost guacConfigParameter: port=5900 guacConfigParameter: password=secret member: cn=user1,ou=people,dc=example,dc=net member: cn=user2,ou=people,dc=example,dc=net
The new connection can then be created using the ldapadd utility:
$ldapadd -x -Dcn=admin,dc=example,dc=net-W -fexample-connection.ldifEnter LDAP Password: adding new entry "cn=Example Connection,ou=groups,dc=example,dc=net"$
Where cn=admin,dc=example,dc=net is an administrator
account with permission to create new entries, and
example-connection.ldif is the name of the
.ldif file you just created.
There is, of course, no need to use only the standard LDAP utilities to create connections and users. There are useful graphical environments for manipulating LDAP directories, such as Apache Directory Studio, which make many of the tasks given above much easier.