[ 
https://issues.apache.org/jira/browse/GUACAMOLE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Couchman updated GUACAMOLE-220:
------------------------------------
    Priority: Major  (was: Minor)

> Implement user groups
> ---------------------
>
>                 Key: GUACAMOLE-220
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-220
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: Documentation, guacamole, guacamole-auth-jdbc, 
> guacamole-auth-ldap, guacamole-ext
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>             Fix For: 1.0.0
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from 
> [GUAC-1073|https://glyptodon.org/jira/browse/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.
> {panel}
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to