Closed quasis closed 2 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Thanks for the clear description! I think I'll go for a close here though. I think reasoning about this may belong in the project working with the local users.
I'm not sure whether this feature request belongs here, it sort of falls between two (or even 3) chairs.
There is plugin out there, that combines between LDAPAuthenticator and LocalAuthenticator. It is a 1 line project, that inherits both authenticators in order to create a local posix user once he was authenticated against some LDAP server. The only problem with this "combined" authenticator, is that local UIDs are arbitrary and dont match the UIDs stored on the LDAP server.
Now, LocalAuthenticator has support for UID maps, you can do the following:
So theoretically, if LDAPAuthenticator could retrieve the UID of the user and populate
uids
field, with bindDN-UID pair, the problem would be solved.