FloatingPanel being closed on HTML5 logoff
Posted: Thu Sep 29, 2016 6:44 pm
Hi.
I have just updated one of our servers to version 9.50.9.22.
We have many others to update, but will hold on until we clarify this case.
Our configuration sets to "Terminate any disconnected session after" 60 minutes. "Only one session per user. The second session will capture the first one".
We only give access through HTML5 and we publish the "FloatingPanel" and a couple of applications of ours.
So, before this last update, a user would log on, work, and if they lost connection or just closed the browser, once they got back (within 60 minutes) they would have their session in the same state, which is perfect. Also, they could close our application, and since the FloatingPanel has a Log Off choice, they might choose it, log off, and come back later. When they proceeded this way, on next log on (within 60 minutes) they would get their last session, which would be an empty desktop, but still with FloatingPanel running on it, and they could call our application.
Now, after the update, closing the browser and coming back later still works and they get their session back from where they left it. But, on the other hand, if they choose the Log Off from the FloatingPanel, once the session is Disconnected on the server, FloatingPanel is being closed and therefore, if they get back within 60 minutes, their session will have an empty desktop WITHOUT FloatingPanel running on it, and from there they can do nothing, since the FloatingPanel is their only access to the applications. We would have to go to the server and manually sign them out.
Please, how can I get the FloatingPanel always running during the session as it happened before like many other process that carry on running after the disconnection?
Thanks in advance.
Ivan
I have just updated one of our servers to version 9.50.9.22.
We have many others to update, but will hold on until we clarify this case.
Our configuration sets to "Terminate any disconnected session after" 60 minutes. "Only one session per user. The second session will capture the first one".
We only give access through HTML5 and we publish the "FloatingPanel" and a couple of applications of ours.
So, before this last update, a user would log on, work, and if they lost connection or just closed the browser, once they got back (within 60 minutes) they would have their session in the same state, which is perfect. Also, they could close our application, and since the FloatingPanel has a Log Off choice, they might choose it, log off, and come back later. When they proceeded this way, on next log on (within 60 minutes) they would get their last session, which would be an empty desktop, but still with FloatingPanel running on it, and they could call our application.
Now, after the update, closing the browser and coming back later still works and they get their session back from where they left it. But, on the other hand, if they choose the Log Off from the FloatingPanel, once the session is Disconnected on the server, FloatingPanel is being closed and therefore, if they get back within 60 minutes, their session will have an empty desktop WITHOUT FloatingPanel running on it, and from there they can do nothing, since the FloatingPanel is their only access to the applications. We would have to go to the server and manually sign them out.
Please, how can I get the FloatingPanel always running during the session as it happened before like many other process that carry on running after the disconnection?
Thanks in advance.
Ivan