On Mon, Mar 16, 2020 at 8:00 PM Vieri <[email protected]> wrote:
> On Tuesday, March 17, 2020, 12:45:34 AM GMT+1, Nick Couchman < > [email protected]> wrote: > > > This is the default, and designed, behavior of the Guacamole Client, if > 1) the user only has access to a single connection, and 2) the user is not > an administrative user. If both of > > these conditions are met, the Guacamole Client will automatically > redirect to the only connection the user has access to. As soon as the > user has access to another connection, > > or is made an administrative user, they will be taken to the home > screen, instead. > > Well, I'm pretty sure this user has more than one connection object. > Also, I'm using LDAP for both auth and connections so, as I understand it, > there's no administrative user. > Well, that takes out the admin user piece of that, so any users that are seeing that behavior likely only have access to one connection - this is the design for how it behaves. I would check those users who are seeing this and make sure they really have access to all the connections you expect. You can check the Ctrl-Shift-Alt hidden menu and go to the Home screen and see. It certainly isn't out of the realm of possibility that there's a bug in Guacamole - we've had one or two before :-). > In any case, I "extended" the connectins list web page and added a section > below it that points to corporate web resources. Even if the user had only > one connection object, I'd still like for he/she to be able to actually see > and access that section. So, even if the design makes sense, the fact that > guacamole is extendable sort of clashes with that. > Even "extending" the home page in such a way that provides additional information or details or links won't change this behavior at this time - if the user has only a single connection, they will get redirected to that connection. That said, while I think that, in general, this behavior is beneficial and desired, and not something I'd want to remove entirely, i can see your point, and maybe there are other circumstances we want to think about that we could change this behavior - either a parameter in guacamole.properties that allows you to disable it (leaving it enabled as the default), or something in a custom extension or branding that would allow for disabling this behavior. -Nick
