There must be some way for authenticated (via github) users to access the MIMIC database from their jupyterhub notebooks.
Options:
Only users who are cleared to access MIMIC db are invited to a github application. Then everyone who clears github auth for that application is guaranteed to be authorized to access MIMIC. Then we can just give all the notebooks access to MIMIC, relying on the github auth for security.
Anyone can get invited to the github app. A secure form on chatto.io allows a particular user to enter their MIMIC username and password. The web server then enables mimic access for that user's notebooks only, using their username and password.
I strongly prefer 1 as an interim solution for the datathon. There's no reason to be on the notebooks without MIMIC access. We would need to coordinate with the mimic team to ensure only authorized folks get invited to the github app.
@tompollard any thoughts on this? Basic proposal is use a github application to mediate access to the MIMIC database. People who are authorized to access MIMIC get invited to the application, no one else does. On the Postgres server side, there's one user with database read access corresponding to the github application. All accesses through chatto appear as this user.
There must be some way for authenticated (via github) users to access the MIMIC database from their jupyterhub notebooks.
Options:
I strongly prefer 1 as an interim solution for the datathon. There's no reason to be on the notebooks without MIMIC access. We would need to coordinate with the mimic team to ensure only authorized folks get invited to the github app.
@tompollard any thoughts on this? Basic proposal is use a github application to mediate access to the MIMIC database. People who are authorized to access MIMIC get invited to the application, no one else does. On the Postgres server side, there's one user with database read access corresponding to the github application. All accesses through chatto appear as this user.