You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Florian <Fl...@nexus-eundl.com.INVALID> on 2024/02/25 10:08:02 UTC
Understanding the permission system to delegate permissions
Hi together,
In my scenario, I have two other users who want to give external people the possibility to test something in our demonstration environment. I gave them the permission to add new users and now they are able to create users, but they cannot assign connections to them. Even not when I permit them to create new connections. I must admit, I don't really understand the permission system of guacamole, es far as I can see you can only permit someone to create new things, and manage them, but he can't "edit" any existing. In my case, this makes it difficult, as I don't want the users to have the possibility to create new connections or change them, but I want them to be able to "use" them and assign them to accounts they created. Is there any way to achieve this?
I use guacamole 1.5.4 in a Docker environment with postgres authentication.
Thanks in advance and best regards,
Florian
Re: Understanding the permission system to delegate permissions
Posted by Michael Jumper <mj...@apache.org>.
On 2/25/24 11:09, med ahmed wrote:
> Hi,
>
> I am also struggling with permission delegation, I would like to allow
> users to view their connections history, Could anyone please tell me how
> to do it?
>
This is an entirely different matter and relates to how the webapp UI
presents itself, not to permission enforcement/delegation.
The webapp UI currently only shows the connection history tab if you are
a system administrator, but this is purely cosmetic and not tied
permission enforcement. It's just the UI choosing to not show a tab
under the assumption that it's mainly relevant to system administrators.
If you think this is also usefully relevant to non-administrative users
and should be made visible within the UI, then that would be a feature
request.
If curious: the permissions that dictate whether a particular connection
history entry is readable are whether the user attempting to retrieve it
has "READ" permission for both the associated user and the associated
connection. If a non-administrative user retrieves the history, their
history view is restricted based on those permissions.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Understanding the permission system to delegate permissions
Posted by med ahmed <me...@gmail.com>.
Hi,
I am also struggling with permission delegation, I would like to allow
users to view their connections history, Could anyone please tell me how to
do it?
Best Regards,
On Sun, Feb 25, 2024, 4:53 PM Michael Jumper <mj...@apache.org> wrote:
> On 2/25/24 02:08, Florian wrote:
> > Hi together,
> >
> > In my scenario, I have two other users who want to give external people
> > the possibility to test something in our demonstration environment. I
> > gave them the permission to add new users and now they are able to
> > create users, but they cannot assign connections to them. Even not when
> > I permit them to create new connections. I must admit, I don’t really
> > understand the permission system of guacamole, es far as I can see you
> > can only permit someone to create new things, and manage them, but he
> > can’t “edit” any existing. In my case, this makes it difficult, as I
> > don’t want the users to have the possibility to create new connections
> > or change them, but I want them to be able to “use” them and assign them
> > to accounts they created. Is there any way to achieve this?
> >
> > I use guacamole 1.5.4 in a Docker environment with postgres
> authentication.
> >
>
> Only an account with full system administrator permissions can directly
> assign permissions related to users/connections that they didn't create
> themselves.
>
> You could give the user(s) in question permission to create user groups.
> They would then be able to add/remove people within those groups so long
> as they are the ones that created those users. You would then use your
> own system administrator account to assign connections to the relevant
> groups. This way, only you would be able to control which specific
> connections apply, yet the users that created the user groups would
> still be able to control which of their own users inherit those
> permissions.
>
> - Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
>
Re: Understanding the permission system to delegate permissions
Posted by Michael Jumper <mj...@apache.org>.
On 2/25/24 02:08, Florian wrote:
> Hi together,
>
> In my scenario, I have two other users who want to give external people
> the possibility to test something in our demonstration environment. I
> gave them the permission to add new users and now they are able to
> create users, but they cannot assign connections to them. Even not when
> I permit them to create new connections. I must admit, I don’t really
> understand the permission system of guacamole, es far as I can see you
> can only permit someone to create new things, and manage them, but he
> can’t “edit” any existing. In my case, this makes it difficult, as I
> don’t want the users to have the possibility to create new connections
> or change them, but I want them to be able to “use” them and assign them
> to accounts they created. Is there any way to achieve this?
>
> I use guacamole 1.5.4 in a Docker environment with postgres authentication.
>
Only an account with full system administrator permissions can directly
assign permissions related to users/connections that they didn't create
themselves.
You could give the user(s) in question permission to create user groups.
They would then be able to add/remove people within those groups so long
as they are the ones that created those users. You would then use your
own system administrator account to assign connections to the relevant
groups. This way, only you would be able to control which specific
connections apply, yet the users that created the user groups would
still be able to control which of their own users inherit those permissions.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org