You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the service process (and hub) restarts, the currently logged-in user is 'forgotten' and asked to log in again. We should find a way to persist that.
The text was updated successfully, but these errors were encountered:
yuvipanda
added a commit
to yuvipanda/jupyterhub
that referenced
this issue
Apr 8, 2021
When an oauth client changes, we delete all the tokens
associated with that client. This invalidates all user sessions
for that oauth client, and the oauth client's users will need to
go through the OAuth workflow again after the cache period (specified
by cache_max_age in HubAuth, 5min by default). This is fine in theory,
since oauth client information doesn't change frequently.
However, we were deleting and re-adding all oauth clients each time
the hub started! This was unnecessary, since the data was going to
be the same 99% of the time. Rest of the time, we should just update,
preventing unnecessary churn.
This PR does that.
Ref yuvipanda/jupyterhub-configurator#2
Ref berkeley-dsep-infra/datahub#2284
When the service process (and hub) restarts, the currently logged-in user is 'forgotten' and asked to log in again. We should find a way to persist that.
The text was updated successfully, but these errors were encountered: