[
https://issues.apache.org/jira/browse/GUACAMOLE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942131#comment-15942131
]
James Muehlner commented on GUACAMOLE-255:
------------------------------------------
I'd have to say that I agree with [~mike.jumper] on this one. If you want to
always access a certain connection, but still have access to others,
bookmarking (or sharing) the link for the desired connection seems to work just
fine. Adding another feature to do essentially the same thing does feel like
feature creep.
[[email protected]] Would that not work for your needs?
> 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)
