You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At some point we'll need MAAP Auth and VEDA Auth to either align or be compatible to enable login to MAAP Hub (2i2c), and access to services the same way it works on VEDA (STAC transactions, etc...).
MAAP will have some additional services, like federation with ESA, and access to MAAP APIs like DPS job management.
Acceptance criteria
Clarify the needs for alignment between MAAP and VEDA and record them in the form of use cases
The text was updated successfully, but these errors were encountered:
Login of MAAP users to MAAP Hub (migration from MAAP ADE to hub is a prime time to do this, aka Next 6 months)
Delegation of MAAP users to research groups, users may belong to multiple research groups. This authorization will determine which DPS queues and which shared buckets a user can use.
MAAP DPS API access (currently via a MAAP token injected into the session on boot)
MAAP user access to various STAC ingestion APIs to publish/edit STAC records.
MAAP federated access across NASA and ESA platforms. <- @smarru can probably explain the details of this better based on the meeting today with ESA.
These requirements for MAAP towards auth (in particular user groups, shared buckets, etc.) is what is developed under EOEPCA as the Workspace Building Block.
This building block provides services like provisioning, lifecycle management, quota, etc. of resources for groups of users, relying heavily on KeyCloak. It includes a UI for managing these resources.
I think their solution is pretty solid and we should really look into using it for VEDA.
The only caveat is that it builds on Kubernetes, like all EOEPCA building blocks - but so does our JupyterHub solution.
Would you be interested in exploring a match between what this solution provides and the requirements we see arising from MAAP, @wildintellect?
Context
At some point we'll need MAAP Auth and VEDA Auth to either align or be compatible to enable login to MAAP Hub (2i2c), and access to services the same way it works on VEDA (STAC transactions, etc...).
MAAP will have some additional services, like federation with ESA, and access to MAAP APIs like DPS job management.
Acceptance criteria
The text was updated successfully, but these errors were encountered: