Central Jupyter facilities

[menzowindhouwer]

Anyone, any scholar, can run a Python notebook and work with open APIs that CLARIAH offers. However to provide access to APIs that require authentication before authorising access to restricted/ipr content, we need to host a Python notebook environment that we are able to extend with an authentication layer that interacts with the central authentication server (SATOSA).

For this task a Jupyter Hub (or another stack that offers a way to host Jupyter notebooks) needs to be installed within the CLARIAH k8s cluster.

The addition of the authentication layer is addressed in another issue (TODO figure out if it was already written, otherwise create one)

[proycon]

Tagging this as FAIR Distribution & Deployment as well, since it's mostly a deployment issue (a Jupyter Hub installation I imagine).

[jblom]

@menzowindhouwer @mmisworking @proycon added a description to this issue. I hope it makes sense to you as well.

[proycon]

I've set something similar up in LaMachine, including OpenID Connect connections to the central authentication provider (not delegation!), so I'll join this as I aim to pull it 'out of' LaMachine anyway (proycon/LaMachine#214)