django-authenticator-gdaley 0.1.5a0

Authenticate to JupyterHub using an active Django login session

JupyterHub django-session-authenticator - A Django Session Authenticator for JupyterHub

Authenticate to JupyterHub using an active Django login session, which was created by a Django-based service running on a server in the same domain as the JupyterHub service.

Prerequisites

The main purpose of this authenticator is to provide single sign-on (SSO) capability into JupyterHub, in cases where users are already authenticating with a web application based on the Django framework. This is a simpler alternative to a more centralized authentication solution, such as Cognito.

To allow this JupyterHub (and this authenticator) to "see" the session cookie generated by Django:

• Django and JupyterHub must be hosted under the same domain. For example, django.hostname.com and jupyterhub.hostname.com
• Django's SESSION_COOKIE_DOMAIN must be set to allow cross-domain cookies. For example, hostname.com

Note that only MySQL database-backed sessions are supported at present.

Installation

This package can be installed with pip:

pip install django-authenticator-gdaley

Alternately, you can clone the source repository and run:

cd django-authenticator
pip install -e .

Configuration

You should edit your file jupyterhub_config.py to set the authenticator class. The DjangoSessionLocalAuthenticator provides features such as local user creation. If you already have local users then you may use the DjangoSessionAuthenticator authenticator class, as follows:

For authentication and local user creation

c.JupyterHub.authenticator_class = 'djangoauthenticator.djangoauthenticator.DjangoSessionLocalAuthenticator'

This class is derived from LocalAuthenticator and therefore provides features such as the ability to add local accounts through the admin interface if configured to do so.

For authentication of the Django session only

c.JupyterHub.authenticator_class = 'djangoauthenticator.djangoauthenticator.DjangoSessionAuthenticator'

Required configuration

There are a number of configuration settings, which need to be made. The name of the session cookie used by Django is optional. If you are using the default session cookie name ("sessionid"), there is no need to set it here.

# Django session cookie name
c.DjangoSessionAuthenticator.django_session_cookie_name = '<insert-session-cookie-name-here>'
# Django MySQL database hostname
c.DjangoSessionAuthenticator.mysql_hostname = '<insert-db-hostname-here>'
# Django MySQL username
c.DjangoSessionAuthenticator.mysql_username = '<insert-db-username-here>'
# Django MySQL password
c.DjangoSessionAuthenticator.mysql_password = '<insert-db-password-here>'

Issues

If you have any issues or bug reports, all are welcome in the issues section. We'll do our best to respond quickly.

Contribution

If you want to fix the bugs yourself then raise a PR and we'll take a look :)