Dave Hirschfeld
Dave Hirschfeld
If you would post your configuration someone may actually be able to help, otherwise as mfriedmann says you may have to look at the commits yourself to see if any...
It looks like you're authenticating correctly: ``` [I 2019-03-29 09:32:36.703 JupyterHub base:499] User logged in: firstname.lastname ``` ...and that the issue is with the spawner: ```python-traceback Traceback (most recent call...
That sounds sensible though whether or not it requires a restart is probably up to JupyterHub
The text which follows after ``` Traceback (most recent call last): ``` ...contains the actual traceback which would enable someone to potentially help diagnose the issue.
I think this is a dup of https://github.com/jupyterhub/ldapauthenticator/issues/148.
You need to show your full config (redacting any sensitive info) if you want anyone to be able to help you
Since your `dn` has `uid` it looks like you're using OpenLDAP in which case you need to specify that as the [`user_attribute`](https://github.com/jupyterhub/ldapauthenticator#ldapauthenticatoruser_attribute). MAybe try the below: ``` c.LDAPAuthenticator.user_attribute = 'uid'...
No idea sorry - I think your best bet to debug it is to pass your config directly to the unerlying `ldap3` library as shown in https://github.com/jupyterhub/ldapauthenticator/issues/116#issue-407542672 You're likely to...
This can probably be closed to reduce noise in the issues list
It seems this may require configuring a custom `SSLContext` http://ldap3.readthedocs.io/ssltls.html#sslcontext