The role of the UI server in production from a user (and permissions) point of view (cylc8)

We have a release!

This upgrades cylc-uiserver to work with Jupyter Hub v4.0+. The documentation has been updated to show how to set up multi-user deployments with Cylc authorisation.

https://cylc.github.io/cylc-doc/stable/html/user-guide/sharing-access-to-workflows.html

Quick overview:

  • Cylc UI Server now works with the latest Jupyter components.
  • Jupyter Hub can now be configured to allow users to spawn each others servers.
  • This means you can authorise a user to spawn and access a server for an “auser” account which they are not able to log into themselves.

There is one barrier you’ll hit with those “auser” accounts which I mentioned somewhere further up this thread. At present Jupyter Hub requires a users to be registered before it will spawn UI Servers for them. Users are automatically registered when they first authenticate with Jupyter Hub. Alternatively, users can be registered via the Jupyter Hub API which is handy for “auser” acounts:

2 Likes