Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hub: utility for populating user records? #468

Open
oliver-sanders opened this issue Jul 17, 2023 · 2 comments
Open

hub: utility for populating user records? #468

oliver-sanders opened this issue Jul 17, 2023 · 2 comments
Milestone

Comments

@oliver-sanders
Copy link
Member

Jupyter Hub allows us to delegate the permissions for one user to start another users server.

This is great, however, for this functionality to work, the user who's server is being spawned must first log into the Hub. This creates an entry in the DB for them which is presumably required in order for another user to spawn their server?

This is inconvenient, but manageable in most cases. Users must log in to set up the hub, after that no further interaction is required until the hub is restarted?

However, in some cases we may have user accounts which can't be directly logged into. In these cases we need to initialise the hub to spawn servers some other way.

Related to #275

@oliver-sanders oliver-sanders added this to the pending milestone Jul 17, 2023
@oliver-sanders
Copy link
Member Author

Looks like Jupyter Hub [now?] has an api for creating multiple users (POST /users) which should be able to fulfil this function.

If this does the trick, then this is just a setup problem (once users are created they should be preserved across restarts by the DB).

https://jupyterhub.readthedocs.io/en/stable/reference/rest-api.html#operation/post-users

@oliver-sanders
Copy link
Member Author

Administrators can add/remove uses provided they are granted the admin:users scope.

This is sufficient to register "shared" user accounts (accounts with no login which are accessed via sudo). If granting the admin:users, make sure to upgrade to the latest version of JupyterHub (a CVE affects this scope in older releases).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant