With regards to the Jupyter issue, this is due to Immerse and Jupyter Lab not sharing the same logout function. If you wish to change users, it’s necessary to clear the cookies for the Immerse URL after logging out through the Immerse interface. It should also be possible to log out of Jupyter Lab as well (through the Lab interface) prior to logging out of Immerse. Note that even if the user is able to launch into the other user’s Jupyter Lab container, they will not be able to use the predefined OmniSci connection object
con as the session would have been terminated by Immerse, so they should have no access to OmniSciDB as that user if it’s being used as designed.
Your Jupyter Lab container should keep running in the background if you log out, however if the Lab container is stopped for whatever reason then it is automatically removed - noting that the data is persisted since volumes are mounted for the locations in which data is saved and shared. Persisting the containers themselves is possible with a configuration option documented in the
JLAB_CONTAINER_AUTOREMOVE), however it is highly not recommended as it almost always results in obscure messages later when attempting to start containers, and as noted they have been designed to persist all data so that the effect is as if the containers themselves persist. In your case the Admin container should still be running but I it sounds like the built-in
con session might have been used. If so, as noted above, logging out of Immerse will destroy the shared session and any running jobs in Lab will then fail due to the invalid session - this will not stop the container though.
With regards to the low Immerse timeout, that timeout is not the default behavior. It could be that the
idle-session-duration has been set to something very low from the default of 60 mins, ref here.
There is another situation where these types of symptoms can be observed, and that is if one is running multiple Immerse interfaces on different ports with the same IP/URL in the browser address bar. Eg. one on https://immerse.yourdomain.com:6273 and https://immerse.yourdomain.com:16273. In that case every time the browser is switched to the other instance the other one will be logged out (since the cookie domain is shared). If that’s the case, then either the IP can used for one of the urls, different browsers can be used, incognito / private mode can be used for one, or the name of the cookie can be set to different things between instances using the
auth-cookie-name configuration parameter under the
[web] section in
omnisci.conf. It looks like that is not documented so we will ensure that it gets added to the docs.