You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2020/09/19 06:05:00 UTC

[jira] [Assigned] (GUACAMOLE-1021) Top level organizational level of connection group repeated when user is in two groups that contain different hosts

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

Mike Jumper reassigned GUACAMOLE-1021:
--------------------------------------

    Assignee: Mike Jumper

> Top level organizational level of connection group repeated when user is in two groups that contain different hosts
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1021
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1021
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>            Reporter: Jason Keltz
>            Assignee: Mike Jumper
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> A user is in two groups that refer to the same organizational level of the connection group, and different hosts underneath.  The system displays the title of the organization level twice - one of them is greyed out, and the other can be used.  When the user has access to the same organizational level in both groups, only one group should be displayed.
> One connection group top-level is created called "Connect with SSH" which contains 4 hosts.
> Group1 contains the top-level "Connect with SSH" and two of the hosts.
> Connect with SSH
>  * Host 1
>  * Host 2
> Group 2 contains the top-level "Connect with SSH" and the other two hosts.
>  * Host 1
>  * Host 2
> A user in both groups sees:
> + Connect with SSH (greyed out, not selectable)
> + Connect with SSH
>  * Host 1
>  * Host 2
>  * Host 3
>  * Host 4
> Expected Behaviour: User sees "Connect with SSH" only one time.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)