[
https://issues.apache.org/jira/browse/GUACAMOLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308380#comment-16308380
]
Nick Couchman commented on GUACAMOLE-360:
-----------------------------------------
I was thinking about some way to disable automatic reconnection on a
per-connection basis (another connection attribute to control this), but I like
this approach much better.
For killing their own active connections this seems pretty straight-forward -
give users LIST and DELETE permissions on ActiveConnections that belong to
them. Not sure if there are any other changes that have to (or should) happen
on the web UI to make this work - maybe a link or "X" on the home page beside
any connection that has an active connection to close it out?
For joining existing active connections, does this require some sort of Sharing
profile to be (automatically) configured/created, or is there some other way to
just join an existing active connection?
> Autoreconnect only most recent session
> --------------------------------------
>
> Key: GUACAMOLE-360
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-360
> Project: Guacamole
> Issue Type: New Feature
> Affects Versions: 0.9.13-incubating
> Reporter: Matt Prager
> Priority: Minor
>
> I've had an issue with Guacamole where I forget to logoff a VNC session, go
> use a completely different computer or device, try to login to the same
> session and get caught in an "autoreconnect loop" where the new session logs
> off off the old session which then autoreconnects that old session and logs
> off the new session ad inifinitum. There's no way to stop this because, if
> I'm not in front of the computer I forgot to log off, I have no way of
> shutting down that session remotely.
> Since many of us leave tabs open rather than remembering to close them, it
> seems that the behavior should be, in the event of a user trying to
> simultaneously log into the same session, that autoreconnect should only
> apply to the most recent session and the older session should be disconnected
> and remain that way.
> Otherwise, you run into a situation where you were using Guacamole at the
> office to log into a VNC session and are then unable to use Guacamole to log
> into that session from anywhere else which sort of defeats the purpose of
> remote access.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
