search

CLARIAH / clariah-plus

This is the project planning repository for the CLARIAH-PLUS project. It groups all technical documents and discussions pertaining to CLARIAH-PLUS in a central place and should facilitate findability, transparency and project planning, for the project as a whole.
9 stars 6 forks source link

Central Jupyter facilities #64

Open menzowindhouwer opened 2 years ago

menzowindhouwer commented 2 years ago

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 commented 2 years ago

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

jblom commented 2 years ago

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

proycon commented 2 years ago

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 (https://github.com/proycon/LaMachine/issues/214)