Closed MetRonnie closed 4 months ago
But I'm guessing we should set it by default that the owner is allowed to access their own hub?
That feels like a sensible default for Jupyter Hub itself.
Cylc configures Jupyter Hub for Cylc use (e.g. changing the logo so users know what they are logging into, changing the spawner command to run the UIS), but we don't attempt to provide a base configuration for Jupyter Hub itself.
If they haven't configured this as a default, they presumably have a reason not to do so? Or otherwise cover it in their setup instructions which we can link to?
From the Jupyter Hub v5 migration guide:
Prior to JupyterHub 5, JupyterHub Authenticators had the implicit default behavior to allow any user who successfully authenticates to login ... This behavior was considered a too-permissive default ... having the effect that some allow configuration is required for anyone to be able to login. If you want to preserve the pre-5.0 behavior with no explicit allow configuration, set:
In other words, this isn't a Cylc compatibility issue, this is the intentional Jupyter Hub default.
Cylc should not be changing Jupyter Hub defaults without good reason, so I would suggest this is a documentation issue. We should add a link to the relevant Jupyter Hub section in our own setup docs.
Closing as nothing to do
JupyterHub 5.0.0 has been released - https://jupyterhub.readthedocs.io/en/stable/reference/changelog.html
It looks like Cylc Hub pretty much works with jupyterhub 5. However when I started
cylc hub
I got this warningSo I added to my
~/.cylc/uiserver/jupyter_config.py
:But I'm guessing we should set it by default that the owner is allowed to access their own hub?
See also: https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users