mrb1090
September 14, 2023, 11:35am
1
We have a customer who is running JupyterHub in AWS w/SAML SSO enabled. SSO is timing out the web sessions and disconnecting our users from long-running notebook jobs. Looking for a workaround so that when users reconnect their notebook sessions are either persistent or recoverable. Any suggestions would be greatly appreciated.
manics
September 14, 2023, 1:04pm
2
When you disconnect the notebook should continue running in the background. The outputs in the notebook won’t be updated:
opened 07:46AM - 15 Aug 17 UTC
enhancement
pkg:notebook
tag:Server Change
tag:Real Time Collaboration
There's been a lot of requests in the past to:
* Reconnect to a long-running no… tebook and keep receiving new output.
* Reconnect to a notebook running on the server side and recover all output when reconnecting.
I'd like to resurface this issue. To the best of my knowledge, these features have been planned at least since 2015 (earliest reference I found: [link](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jupyter/8hyGKoBY6O0/RyEDDyOZAQAJ)). It hasn't been implemented yet because it directly conflicts with the architecture of the stack and would require a big refactor.
I don't know if this is easier in the JupyterLab context or not. But now that this project is in very active development, it might be a good opportunity to revisit this and try to get it in now at the foundations.
I found to open issues on the topic in the old notebooks repo:
* jupyter/notebook#1150
* jupyter/notebook#641
but if the notebook saves any persistent outputs e.g. files they should be available.
Are you able to modify the SSO timeouts?