Bug 5049 - "End existing session" for Web Access
Summary: "End existing session" for Web Access
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
Depends on:
Blocks: 5060
  Show dependency treegraph
Reported: 2014-03-28 11:32 CET by Karl Mikaelsson
Modified: 2024-03-01 17:08 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Karl Mikaelsson cendio 2014-03-28 11:32:23 CET

Comment 1 Karl Mikaelsson cendio 2014-03-28 11:33:15 CET
Something the native client can do but the HTML5 client can't.
Comment 5 William Sjöblom cendio 2024-03-01 17:08:03 CET
In my understanding, the main difficulty here is that we do not have support for multiple sessions per user in Web Access. That is, we heuristically choose which session to reconnect to if multiple sessions are already running on the server (see bug 5060). Killing the wrong session is far more destructive than reconnecting to the wrong session.

From my point of view, we have two alternatives:

- Letting this snowball into a big project where we add full multi-session support to Web Access.

- Only enable this feature in clusters that allow a maximum of 1 session per user (and bail out if the user despite this has more than 1 session running for some reason).

Only allowing one session per user seems to be the norm, so I think the latter approach is fairly reasonable, especially considering the stance all major DEs have taken against multiple sessions per user.

Note You need to log in before you can comment on or make changes to this bug.