Bugzilla – Bug 5060
Multiple session handling in Web Access
Last modified: 2019-06-17 10:20:41
You need to
before you can comment on or make changes to this bug.
Created an attachment (id=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).
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.
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.