[GUACAMOLE-524] Allow LDAP attributes to be used as token

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Implemented
• Fix Version/s: 1.1.0
• Component/s: Documentation, guacamole-auth-ldap
• Assignee: Nick Couchman
• Reporter: Jared Frees
• Created: 08/Mar/18 19:41
• Updated: 19/Jan/20 01:36
• Resolved: 14/Aug/19 00:44

Description

Add support for using LDAP attributes as tokens for connection configuration.  For example, map the attribute 'workstationName' of the current logged on user to a token USER_WORKSTATION that could then be used in a connection profile.  This would allow using a single connection and for the destination to be determined by the LDAP attribute.  This mapping should be configurable and could be used in a connection definition such as the following:

 
dn: cn=Example Connection,ou=groups,dc=example,dc=net
objectClass: guacConfigGroup
objectClass: groupOfNames
cn: Example Connection
guacConfigProtocol: rdp
guacConfigParameter: hostname=${USER_WORKSTATION}
guacConfigParameter: username=${GUAC_USERNAME}
guacConfigParameter: password=${GUAC_PASSWORD}
member: cn=user1,ou=people,dc=example,dc=net
member: cn=user2,ou=people,dc=example,dc=net

Issue Links

• causes: GUACAMOLE-807 Parameter tokens are not applied by LDAP
• causes: GUACAMOLE-580 Missing null check in LDAP AuthenticationProviderService
• is related to: GUACAMOLE-641 Support storage of sensitive data within key vaults