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

Jason Keltz commented on GUACAMOLE-1021:
----------------------------------------

[~vnick]: I've tested, and the problem is still there.  Quickest way to see it 
is to just put a user X in a group that has access to 1 organizational group 
and say, one connection in that group , then give the same user access to that 
connection directly (via user).  The organizational group will be printed 
twice, one greyed out.

> 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
>            Priority: Minor
>
> 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)

Reply via email to