[jira] [Commented] (GUACAMOLE-220) Implement user groups

["Michael Jumper (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574336#comment-16574336 ] 

Michael Jumper commented on GUACAMOLE-220:
------------------------------------------

Currently seeing a regression in the handling of user creation with multiple data sources. To reproduce:

 # Enable two extensions which support write access (both MySQL and PostgreSQL, for example)
 # Within the admin interface, select a user which exists in one extension but not the other
 # Select the datasource tab for the extension which lacks the user
 # The user interface does not finish loading, instead displaying an infinitely rotating gear.

Something got changed in the logic for automatic user creation. The editor is supposed to automatically set things up for creating a corresponding user if the user account exists in one datasource and not the other, but it is now simply trying to load the user as if it exists already, which naturally fails.

I suspect this is due to my changes aimed at extracting the common code shared across all management screens.

> 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)