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 2021/08/30 17:34:00 UTC

[jira] [Commented] (GUACAMOLE-1410) Two Groups that connect to the same root folder with different connection objects don't merge

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

Mike Jumper commented on GUACAMOLE-1410:
----------------------------------------

Testing this myself, I'm not seeing any issues, and permission inheritance works exactly as expected.

I created a user group, "Group_RDP", with the following connection permissions:

!Group_RDP-contents.png|width=240px!

and a user group, "Group_SSH", with the following connection permissions:

!Group_SSH-contents.png|width=240px!

and a test user with the following group memberships:

!test-user-memberships.png|width=320px!

Logging in as said test user, I see a connection group containing both expected connections, and I am able to connect to each individually.

Are you sure you're using the 1.3.0 versions of both the webapp and the database extension? What you describe sounds in principle like GUACAMOLE-1021, which was fixed as part of 1.3.0.

What internal error are you referring to? What do you see in the Tomcat logs for that error?

> Two Groups that connect to the same root folder with different connection objects don't merge
> ---------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1410
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1410
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.3.0
>         Environment: Ubuntu
>            Reporter: David Haggard
>            Priority: Major
>         Attachments: Group_RDP-contents.png, Group_SSH-contents.png, test-user-memberships.png
>
>
> I've organized my groups based off connection type, SSH, RDP etc. I want some users to have access to one type but not another.  These connection objects live in the same root node.
> Connection root node and connection objects:
> Clients
> - client1_rdp
> - client1_ssh
> Group_Name: Group_RDP
> (checked) Clients
> - client1_rdp (checked)
> - client1_ssh(not checked)
> Group_Name: Group_SSH
> (checked) Clients
> - client1_rdp (not checked)
> - client2_ssh (checked)
> When a user is in Group_RDP and Group_SSH the user can't connect to connections, get an internal error. Or the Connection root doesn't show up at all. It's as if the permissions/groups/connections are not merged for that user. It's not expected behavior and causes problems for the user.
> I can move the connection objects off type to their own root node but I want to consolidate the connection objects into fewer nodes for ease of management/organization.



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