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
We need to be able to distinguish resource consumption (core/RAM hours) for different groups of users of VEDA Hub. This is tracked in 2i2c-org/infrastructure#5315 as a 2i2c platform initiative. To do this, we would need to be able to provide the Relying Party (in this case, JupyterHub) information about all the groups a user belongs to. Different from #128, which can operate at the level of scopes / capabilities / roles (authorization and what they can access) rather than at the group / identity level.
User group this serves
Stakeholders who need to know how well their workshop went
Stakeholders who need to understand how much cloud usage is coming from their group
Description
We need to be able to distinguish resource consumption (core/RAM hours) for different groups of users of VEDA Hub. This is tracked in 2i2c-org/infrastructure#5315 as a 2i2c platform initiative. To do this, we would need to be able to provide the Relying Party (in this case, JupyterHub) information about all the groups a user belongs to. Different from #128, which can operate at the level of scopes / capabilities / roles (authorization and what they can access) rather than at the group / identity level.
User group this serves
Validating application / Relying Party
JupyterHub
Auth requirements
TBD
Solution exists currently
No
Contact person
JupyterHub team / Sanjay / Yuvi
The text was updated successfully, but these errors were encountered: