Description
Bug description
When configuring GoogleOAuthenticator in JupyterHub with allow_all = False and providing a list of allowed users, the allowed users are intermittently denied access. After a few hours of uptime, these users receive a 403 Forbidden error when trying to access the hub.
The issue resolves temporarily after restarting the Hub pod. However, after another few hours, the same problem recurs.
Additionally, in the logs prior to restarting the Hub pod, when an affected user tries to access the hub UI, the following message appears:
User 'X' not allowed.
Even though 'X' is on the allowed users list and was previously able to log in after the last restart.
Your personal set up
zero-to-jupyterhub
- Version(s): Chart Version 3.3.7
Configuration
Auth Configs:
set {
name = "hub.config.Authenticator.auto_login"
value = true
}
set {
name = "hub.config.GoogleOAuthenticator.allow_all"
value = false
}
set {
name = "hub.config.GoogleOAuthenticator.allow_existing_users"
value = true
}
set_list {
name = "hub.config.GoogleOAuthenticator.allowed_users"
value = var.allowed_users *
}
set {
name = "hub.config.JupyterHub.authenticator_class"
value = "google"
}
- allowed_users is a list of user emails (without @email.com) that are allowed to login.
- Removed the client ID, secret ID, and callback URL.