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

Michael Jumper resolved GUACAMOLE-382.
--------------------------------------
    Resolution: Duplicate

> Difficult to manage an install consisting of many users and connections
> -----------------------------------------------------------------------
>
>                 Key: GUACAMOLE-382
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-382
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-jdbc, guacamole-auth-ldap
>    Affects Versions: 0.9.13-incubating
>         Environment: Linux
>            Reporter: Wake Board
>            Priority: Minor
>
> It is very difficult to use guacamole to manage a large install consisting of 
> 40-60 users able to access 40-60 connections.  Adding a new connection 
> requires visiting each user profile separately to add the new host.  
> Would suggest one of two improvements:
> # Improve user management to allow defining roles.  These roles (groups) 
> could allow assigning specific permissions and then the roles are granted to 
> users.  For example, there could be roles for developers, testers, and 
> customers.  Each role unlocks specific connections.  Then just the role is 
> granted to individual ldap accounts.  This would greatly reduce the effort to 
> maintain.
> # Provide (or document) an interface to programmatically allow granting 
> users-to-connections.  This would allow external scripting/management of the 
> connections available to a specific user.  From the outside, a customer could 
> automate assigning the connections that are needed for a specific user.  
> Would need to be able to query, add, and remove connections per user and to 
> be able to enumerate connections available.  Perhaps it could be a REST 
> interface or alternatively details of how to do this via the underlying 
> database.
> Our install consists of using the ldap module for login authentication and 
> the jdbc module for connection information.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to