Bug 5060 - Multiple session handling in Web Access
Summary: Multiple session handling in 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: LowPrio
Assignee: Peter Åstrand
Depends on: 5049
  Show dependency treegraph
Reported: 2014-04-02 10:25 CEST by Karl Mikaelsson
Modified: 2024-03-01 17:08 CET (History)
2 users (show)

See Also:
Acceptance Criteria:

Native tlclient select session dialog (reconnect policy = ask) (18.03 KB, image/png)
2014-04-02 10:25 CEST, Karl Mikaelsson

Description Karl Mikaelsson cendio 2014-04-02 10:25:56 CEST
Created attachment 519 [details]
Native tlclient select session dialog (reconnect policy = ask)

When logging in through the HTML 5 client, you are unable to select which session you want to reconnect to, create a new session, or end an existing session as you can with the native client (depending on the reconnect policy).
Comment 1 Aaron Sowry cendio 2019-06-14 00:58:28 CEST
Just to clarify the current behaviour: if there are multiple sessions available, the browser client will connect to the first "available" (disconnected) session, if there is one. Otherwise, it will connect to and take over the first created session.
Comment 2 Pierre Ossman cendio 2019-06-17 10:20:41 CEST
That last comment is probably not completely accurate. Web Access will only take over a connected session as a last resort. I.e. when all sessions are connected, and it isn't allowed to create any more.

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