Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using exising user accounts?

See original GitHub issue

I didn’t actually try an installation yet, but reading the docs/code as i understand it, this config will always create new users with a jupyter- prefix. We use our server for a range of services so everyone has their own standard linux user account - is it supported to just use the existing user accounts?

Issue Analytics

State:
Created 5 years ago
Comments:6

Top GitHub Comments

1reaction

davide84commented, May 22, 2020

Hi! I’m in the same situation of mangecoeur, I manage a server where home folders are centralized, customized and shared… and having a duplicate set of users and home folders is a no-go. I know this is an old issue, but I guess there could be better solutions to the problem of hijiacking users. First of all, Ubuntu and other distros have no explicit root user 😃 but a more general solution could be to check if a /home folder already exists to validate a legitimate user. cups, www-data and other “system” users don’t have a home folder, only real users do. Hope this can be of interest.

0reactions

davide84commented, Oct 27, 2020

I ended up using JupyterHub with LDAP authentication. Actually, all the users on the server are LDAP accounts, except for the single user defined during OS installation. I don’t use jupyter-xxx accounts at all. So far it’s working as I wanted to…

I followed mangecoeur’s guide for the most part, back in June.