Correct Log out procedure?

Product Help
1

Hi everyone, I started to use Anaconda Cloud Notebooks just today.

A quick question: what is the correct way to completely log out from the notebooks? As far as I have explored the interface I could not find an exit or close button in the notebook page (nb.anaconda.com/jupyterhub/user/[code]).

I logged out from my dashboard with the sign out button (anaconda.com) but the notebook remains connected.

On the top right corner of the notebook intercace there is a green dot with the A. I don’t know if that is something common to everyone (A for Anaconda) or is still my profile (A for my initial name).
However, icon or not, my notebook session, terminal and so on was stil loaded. I tried to close the page and reopen it, and with my surprise the nb.anaconda.com redirected to my usercode still logged in.

As far as I understood, the main dash was logged out succesfully, but the nb.anaconda.com page remain always logged in…
Since I use the cloud notebooks on the go and on different machine, there is a way to terminate the session directly inside the nb.anaconda page? That force nb.anacoda to kick out and not reload my user?

On the same topic, even the numbered terminal remain “logged”. I still have the number 5 in the bottom bar. So event after logging out from anaconda, the notebook remains online and even keep the information about the number of the terminal windows that I have opened.

Update: After the previous log out I cleaned the cache, cookies and so on of the browser. In that way opening the nootebook page redirect to the login page.
When I logged in, I found a cleaner interface with fewer option: no green dot in the top right bar, no bottom bar with “help” or “submit a request” option. No disk and cpu button on the top.
No “Anaconda” buttons on the launcher.
After fews page refresh, a server error came out and then the message “spawning server”.
After that the interface was complete.

So, as far I’ve experimented, the notebook page is a special session that always remain active for a browser. There is no way to terminate a sessione inside the nb.anaconda.com interface.
However, if I quick log out and log in, the server need some time to “spawn”, so I think (or maybe hope) that after some inactivity the notebook actually remains open only visually.

However, if I can suggest a function, an exit or log out features may be nice. Especially since a cloud service is often used on the go.
For example, If I have a google document open, and I logged out on Gmail or Drive, the session kicks me out from the document too since is linked to the account.

Thanks in andvance!

1 Like
2

Hey @Andrea2, thanks for taking the time to detail and experiment here, it’s much appreciated!

Regarding the initial, it should read your initials from your Anaconda Profile. If you go to account settings you should be able to set your name.

Logging out is indeed a bit fiddly, and I appreciate you taking the time to experiment and log the detail here. If you have logged out at anaconda.com, there may be a short window when you can continue to access the cloud notebooks due to the jupyterhub session still being live, this will typically expire after a few hours.

At the moment the only way to force the session to end is via opening a terminal and runningkill 1. This will force you to reauthenticate the next time you try to reach the cloud notebooks. Appreciate it’s not a great user experience so I will work with our engineering teams to see what we can do.

Thanks again,
Jack

2 Likes
3

Thanks @JackEvans, I didn’t know about the comman kill 1. The short window in which the session remains live is something that I had thought about. Still gald that the session will be closed anyway after some time.

The cloud notebooks feel robust, and a “slightly more user friendly” option to exit the notebook may be useful. Or the best thing that comes to mind would be something like the GSuite where a log out in any application (gmail, drive, document, etc.) force the disconnection in every other browser windows related to that profile.

update: I’ve tried the kill 1 and it actually kill the server session asking if the user want to spawn another one.
However, I report that with the Anaconda main page logged in on signed out, if an user click the spawn again/reload button to restart the session, the jupyter lab interface reload. The only difference that I’ve found is in the green dot with the initial at the top right of the page. If the Anaconda main site is not logged in, then that button is not present. But the session is still loaded without asking to log in.
So even if the command effectively kill the session, and the main Anaconda site is not logged in, the jupyter lab server spwan process still reload the previous session (in my case). Even in an Incognito browser window.

Closing the Incognito browser, cleaning the cache and the cookie is still the best way to force the request for a log in.

As far as I’ve experimented, to correct “pipeline” should be:

  • log out from Anaconda main site;
  • kill the session with kill 1in a terminal in jupyter lab cloud;
  • as the message who prompt to spawn a new server connection appear, closing the window and cleaning the cache+cookie (or use an In Incognito browser window).

Thanks you, have a nice day.

Andrea

1 Like