[GUACAMOLE-70] Add option to restrict access to users within database

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.9.11-incubating
• Component/s: guacamole-auth-jdbc
• Assignee: Mike Jumper
• Reporter: Mike Jumper
• Created: 03/Aug/16 22:42
• Updated: 04/Jun/17 17:20
• Resolved: 13/Nov/16 02:10

Description

The LDAP and database authentication backends have been usable together since GUAC-586, but this still causes trouble in the case that only LDAP users that also exist within the database should have access.

There are cases where large deployments of Guacamole involve a large LDAP tree that contains many users, only a subset of which should be granted access to Guacamole. Restructuring the LDAP tree to ensure that only certain users can log in to Guacamole is not always feasible. Rather than universally granting access so long as LDAP accepts the credentials, the database authentication should provide an option to deny access to authenticated users if they do not also have associated data in the database.

It has been verified that extensions can indeed reject an otherwise positive authentication result from a different extension.

Issue Links

• is related to: GUACAMOLE-284 Database "Account Restrictions" not applied when using LDAP
• links to: [GUAC-1539] Allow extensions to veto authentication results
• links to: [GUAC-1553] Add option to restrict access to users within database