Many thanks to developers for this feature! But how and where it should be configured?
This is supported out of the box now (since version 1.1.0) and does not require specific configuration.
I have tried it out with v1.1.0 just now and did not succeed.
I had logged in in two different browser sessions, logged out from one, was automatically logged out from another.
What can i do to troubleshoot it please?
If you explicitly log out of the application, this is expected:
log out logic: should shut down all containers for a given user, so all user-app combinations and therefore all sessions of a single user/app combination
heart beat logic: the container for a particular user/app combination should only shut down if the heart-beat limit is reached for all of the sessions
Hope this helps!
I always wondered is it rational to kill all the containers when the user logouts? We already have a heartbeat mechanism and this sometimes would cause problem if user submits a task and it runs in a future.
Also I’m kind confused by multiple sessions per user/app combination. What does it achieve? It still means one user one app each time, just using different sessions?
This is the rationale behind allowing for multiple sessions per user/app combination:
- a single user/app combination = 1 proxy = 1 container
- multiple sessions (e.g. different browser tabs, different browsers etc.) should be possible to run on a single container
- doing so respects our general tenet that Shiny apps on ShinyProxy function in exactly the same way as Shiny apps that are run locally (where you can also have multiple sessions connecting to the same port in different browser tabs)
- there is no additional security risk compared to having a single session