[
https://issues.apache.org/jira/browse/GUACAMOLE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942115#comment-15942115
]
Michael Jumper commented on GUACAMOLE-255:
------------------------------------------
{quote}
It's mostly a user experience sort of thing. I can think of a few situations -
perhaps not overly concrete examples, but they work in my mind:
- I use Guacamole every day, and 99% of the time I use one connection. I have
3-4 others defined, and use them occasionally, but my Windows VDI connection is
by far the most-used connection. Auto-start seems perfect for that (even
though it would only save me 1 click per login).
{quote}
Why not bookmark the connection in question?
{quote}
- In a previous place of employment where we used Guacamole, we'd be pointing
users (and not the sort with a high level of technical skill) toward a
Guacamole web page and have them log in. We would tell them specifically to
use a certain connection, and most of them would most of the time, but there
would be that small few who couldn't follow instructions. There were other
connections that some of them needed access to, but still would have been nice
to just have it auto-start on the connection we wanted them to use most of the
time, with the option that other folks could disconnection and choose a new
connection if they needed to.
{quote}
Why not send the users a link to the specific connection in question? Or, more
ideally, only give the users access to the connections they should access?
{quote}
I know those are a little on the weak side, and this definitely isn't a
must-have, just seems like there could be scenarios where it's useful for a
more seamless user experience.
{quote}
Ehhhhhhhh... Honestly, this feels more like feature creep to me.
Part of the idea behind ensuring connection URLs were deterministic was to
ensure they would be bookmarkable for this sort of case - where you
consistently want to access a specific connection, despite legitimately having
access to several others. Beyond that, if users are generally not supposed to
access a set of connections, then they really shouldn't be given such access.
I'd be interested to hear what [~frode] and [~james.muehlner] think of this,
but my stance thus far is that, as far as seamlessness is concerned, this would
add more seams than it removes in the majority of cases.
> Support Ability to Auto-Start Connection
> ----------------------------------------
>
> Key: GUACAMOLE-255
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-255
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole
> Reporter: Nick Couchman
> Priority: Trivial
>
> Currently the Guacamole client only automatically starts a connection when a
> single connection is defined for a user/login. It would be useful to set a
> connection to automatically start when a user logs in, even if multiple
> connections are available. The user should still be able to disconnect and
> return to the home screen, but there are certainly situations where it is
> desirable to have an automatic connection happen at login.
> As I see it there are two possible routes for implementing this:
> - Set up a connection parameter or attribute for auto-starting and have the
> client check connections at login time for the attribute and start them.
> - Set up a user-specific field for a connection to auto-start, and store the
> connection id (hash of datasource + id + type) in that field, and have the
> client check for that property at login and locate/start the specified
> connection.
> My preference would be to do this at the user level, for the following
> reasons:
> - You could then limit it to 1 auto-start per user, and avoid confusion of
> having multiple connections available to a user marked for auto-start and
> having to determine which one(s) you actually start.
> - The user can be in control of whether or not a connection is automatically
> started, and, if so, which one. There doesn't seem to be any
> security-relevant implications for allowing the user to control this - the
> necessary checks should still be in place to make sure the user is only
> starting a connection he has access to, and not injecting something bad into
> the field, but whether or not it starts automatically is more of an
> experience topic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
