AD configuration, need help!

[majid35]

Hello guys,

I am trying to setup AD with Jupyterhub but I am stuck on the AD configuration and I am not able to connect. Below is my config and the error message that I get.

Could you please help me the configuration?

Configuration

c.JupyterHub.authenticator_class = 'ldapauthenticator.LDAPAuthenticator'
c.LDAPAuthenticator.server_address = 'IP ADDRESS'
c.LDAPAuthenticator.bind_dn_template = 'cn={USERNAME},ou=BIP,ou=Resources,dc=global,dc=corp,dc=MYCOMPANY'
c.LDAPAuthenticator.lookup_dn = False
c.LDAPAuthenticator.user_search_base = 'dc=global,dc=corp,dc=MYCOMPANY'
c.LDAPAuthenticator.user_attribute = 'sAMAccountName'
c.LDAPAuthenticator.valid_username_regex = '^[a-zA-Z][.a-z0-9_-]*$'
c.LDAPAuthenticator.allowed_groups = []
c.LDAPAuthenticator.server_port = 389

Logs

jupyterhub --no-ssl --log-level=DEBUG
[D 2016-11-23 10:30:02.961 JupyterHub application:555] Looking for jupyterhub_config in /root
[D 2016-11-23 10:30:02.962 JupyterHub application:577] Loaded config file: /root/jupyterhub_config.py
[I 2016-11-23 10:30:03.025 JupyterHub app:724] Loading cookie_secret from /root/jupyterhub_cookie_secret
[D 2016-11-23 10:30:03.026 JupyterHub app:796] Connecting to db: sqlite:///jupyterhub.sqlite
[W 2016-11-23 10:30:03.070 JupyterHub app:365]
Generating CONFIGPROXY_AUTH_TOKEN. Restarting the Hub will require restarting the proxy.
Set CONFIGPROXY_AUTH_TOKEN env or JupyterHub.proxy_auth_token config to avoid this message.

[W 2016-11-23 10:30:03.080 JupyterHub app:864] No admin users, admin interface will be unavailable.
[W 2016-11-23 10:30:03.080 JupyterHub app:865] Add any administrative users to c.Authenticator.admin_users in config.
[I 2016-11-23 10:30:03.081 JupyterHub app:892] Not using whitelist. Any authenticated user will be allowed.
[D 2016-11-23 10:30:03.093 JupyterHub app:1082] Loading state for i329537 from db
[D 2016-11-23 10:30:03.093 JupyterHub app:1094] i329537 not running.
[D 2016-11-23 10:30:03.093 JupyterHub app:1099] Loaded users:
i329537
[I 2016-11-23 10:30:03.102 JupyterHub app:1450] Hub API listening on http://127.0.0.1:8081/hub/
[W 2016-11-23 10:30:03.106 JupyterHub app:1171] Running JupyterHub without SSL. I hope there is SSL termination happening somewhere else...
[I 2016-11-23 10:30:03.106 JupyterHub app:1173] Starting proxy @ http://:8000/
[D 2016-11-23 10:30:03.107 JupyterHub app:1174] Proxy cmd: ['configurable-http-proxy', '--ip', '', '--port', '8000', '--api-ip', '127.0.0.1', '--api-port', '8001', '--default-target', 'http://127.0.0.1:8081', '--error-target', 'http://127.0.0.1:8081/hub/error']
10:30:03.218 - info: [ConfigProxy] Proxying http://:8000 to http://127.0.0.1:8081
10:30:03.220 - info: [ConfigProxy] Proxy API at http://127.0.0.1:8001/api/routes
[D 2016-11-23 10:30:03.315 JupyterHub app:1202] Proxy started and appears to be up
[I 2016-11-23 10:30:03.316 JupyterHub app:1482] JupyterHub is now running at http://127.0.0.1:8000/
[W 2016-11-23 10:30:13.826 JupyterHub ldapauthenticator:92] Invalid username
[D 2016-11-23 10:30:13.826 JupyterHub login:95] Failed login for USERNAME

Thanks a lot!
Majid

[majid35]

Any help guys?

[yuvipanda]

What was the username you were using? Ldapauthenticator by default restricts usernames to those that match the following regex: '^[a-z][.a-z0-9_-]*$'. This is to protect against LDAP injection attacks. The particular error you are seeing is when the username supplied does not match this. You can set the value for this regex with: c.LDAPAuthenticator.valid_username_regex = r'<yourregex>'. See if that helps? Don't set it to .* tho, set it to the minimal regex that matches all your user's names.

…

On Fri, Nov 25, 2016 at 1:05 AM, majid35 ***@***.***> wrote: Any help guys? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB23lBrTg6QCKiMCE0sq5wM8IGBXe-Hks5rBqTTgaJpZM4K6bmG> .

-- Yuvi Panda T http://yuvi.in/blog

[ixxie]

FWIW I have managed to get it working and outlined instructions at #54.

[dhirschfeld]

Closing as stale. If after the latest release (#70) you're still having problems please feel free to open a new issue.