[GUACAMOLE-26] Add support for overall concurrency limits

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Done
• Fix Version/s: 0.9.10-incubating
• Component/s: Documentation, guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, guacamole-auth-jdbc-postgresql, guacamole-docker
• External issue URL: https://glyptodon.org/jira/browse/GUAC-1512
• Assignee: Unassigned
• Reporter: Mike Jumper
• Created: 19/May/16 06:09
• Updated: 03/Sep/16 02:44
• Resolved: 19/May/16 06:09

Description

The description of this issue was copied from GUAC-1512, an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the Apache Incubator.

Comments, attachments, related issues, and history from prior to acceptance have not been copied and can be found instead at the original issue.

Guacamole currently supports concurrency limits at a per-connection level and a per-user level, but not overall. If the absolute total number of connections to a Guacamole server must be limited to a specific amount, this is impossible in the current system. This is particularly important if the licensing of some proprietary remote desktop server prohibits greater than a certain number of connections, but there are multiple Guacamole connections pointing to this server.

An additional property, like "mysql-max-connections" and "postgresql-max-connections", would satisfy this need.