Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-add workflow 5 #144

Merged
merged 3 commits into from
Jan 8, 2025
Merged

Re-add workflow 5 #144

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a9017c0
Re-add workflow 5
yuvipanda Dec 21, 2024
f572a75
Add an explanatory note
yuvipanda Dec 21, 2024
8eed8ff
Update docs/use-case-evaluation/workflows.md
yuvipanda Jan 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 32 additions & 1 deletion docs/use-case-evaluation/workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,4 +131,35 @@ Depending on the Relying Party, mapping groups to roles / capabilities could be
#### Documentation on this workflow

1. Keycloak -> (provide link)
2. Custos / veda-auth-central -> (provide link)
2. Custos / veda-auth-central -> (provide link)


### Workflow 5: User Profiles for credential storage

#### Use cases served

[7](https://github.com/NASA-IMPACT/veda-auth-central/issues/129),
yuvipanda marked this conversation as resolved.
Show resolved Hide resolved
[8](https://github.com/NASA-IMPACT/veda-auth-central/issues/130),
[9](https://github.com/NASA-IMPACT/veda-auth-central/issues/131),
[10](https://github.com/NASA-IMPACT/veda-auth-central/issues/132)

#### Description

We want to provide a place where users can store specific authentication tokens for third party services (such as DPS jobs or Earthdata login or other HPC systems). End users need a UI where they can store these tokens, and specific services that have permissions to retrieve these should be able to retrieve them.

#### Frequency of use

Based on our current set of use cases, this is only used by people who are trying to do something reasonably advanced - access external compute resources from within our compute resources. So not frequent yet.

#### Who would perform this workflow?

1. End Users would need to use this UI to enter any tokens they have
2. Relying Party Maintainers would need to configure wether they need access to any specific tokens or not.

For example, if JupyterHub wants to get access to the earthdata login token and the DPS token, the JupyterHub
maintainers would need to configure their server to fetch it as appropriate.

#### Documentation on this workflow

1. Keycloak -> (provide link)
2. Custos / veda-auth-central -> (provide link)