[
https://issues.apache.org/jira/browse/GUACAMOLE-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406955#comment-17406955
]
David Haggard commented on GUACAMOLE-1410:
------------------------------------------
The database auth extension was v1.0.0 while the rest of the system was 1.3.0.
This is likely due to an odd problem that happened a few months back on
digitalocean. This server was Ubuntu 18.04 which I installed Guac starting from
1.0.0. I've updated guac as major releases came out so it was running 1.3.0 for
awhile. I logged into the server due to a reported problem one day and noticed
that guac was running v1.0.0 of the executable like the server was reverted
back to a very old backup. I did an inplace upgrade to v1.3.0 and I guess I
didn't replace the extension file for the database so that was this issue.
I rebuilt this server to Ubuntu 20.04 and guac is now running and I did test
the groups and it's working as expected, thank you.
> 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)
