Details
-
Feature
-
Could have
-
None
-
SRCnet
-
-
-
1
-
1
-
0
-
Team_TANGERINE
-
Sprint 4
-
-
-
-
22.6
-
Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
science-gateway
Description
The science gateway currently allows users to search for, and launch, instances of a JupyterHUB notebook on SRCNet resources. However, upon launching the notebook the user will be asked to sign into the SKA IAM again, which is not consistent with our requirement to provide a single-sign-on platform environment.
In each instance of JupyterHUB we can generate user-access tokens, which can be passed to the JupyterHUB url as query parameters in order to log the user in automatically.
We therefore require a database to store these tokens, on a per-user and per-JupyterHUB-instance basis, and to make them available to the science gateway via a new API. A call to the API must be authenticated by providing a suitable token from the Auth APIs in order to confirm that the caller is authorised to access this JupyterHUB token, but the exact process is to be determined.