Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Done
-
None
-
None
Description
The description of this issue was copied from GUAC-1073, 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 should support tagging of users into logical user groups, such that permissions can be managed at a group level, rather than a per-user level. These permissions should include all available permission types, not simply "READ' as in the current management interface.
With this in mind, the permission manipulation interface would need to be modified to support a more standard ACL-style interface at the connection level, allowing users or groups to be added to a connection, rather than connections added to a user or group.
Attachments
Issue Links
- is duplicated by
-
GUACAMOLE-209 Working with groups of users and connections
- Resolved
-
GUACAMOLE-207 default connection
- Resolved
-
GUACAMOLE-382 Difficult to manage an install consisting of many users and connections
- Resolved
-
GUACAMOLE-562 Allow filtering of connections by whether access is granted
- Resolved
-
GUACAMOLE-182 User Groups
- Resolved
- is related to
-
GUACAMOLE-541 Webapp dependencies take precedence over bundled extension dependencies
- Resolved
-
GUACAMOLE-749 Filter affects only the first level of the connection permission editor tree
- Resolved
-
GUACAMOLE-542 Provide base implementations of UserContext and AuthenticationProvider
- Resolved
-
GUACAMOLE-635 Build against and require Java 1.8
- Resolved