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.

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

UC-05: Group membership management #127

Open
j08lue opened this issue Oct 17, 2024 · 3 comments
Open

UC-05: Group membership management #127

j08lue opened this issue Oct 17, 2024 · 3 comments
Assignees
Labels

Comments

@j08lue
Copy link
Collaborator

j08lue commented Oct 17, 2024

Description

A platform administrator can add and remove users from a group they manage

Focus use case: group membership administration for JupyterHub access

As a workshop lead, I am able to log into a simple enough interface and administer membership for a group of participants, so I can get workshop participants set up with the resources they need.

User group

  • Privileged platform users
    • e.g. the host of a workshop that is relying on VEDA JupyterHub

Validating application / Relying Party

IAM / Auth admin interface

Auth requirements

  1. An privileged user is able to manage group membership for a predefined group
  2. The privileged user does NOT need to be able to create the group and edit its permissions - that an ops team member can do.
  3. The privileged user can disable group access or delete the group (e.g. after workshop or other event is over).

Solution exists currently

Yes, we currently use GitHub teams on arbitrary GitHub orgs and through these delegate membership management to workshop hosts.

Contact person

JupyterHub team / Sanjay / Yuvi

@j08lue
Copy link
Collaborator Author

j08lue commented Oct 18, 2024

@yuvipanda, would you please review / complete the description and requirements above?

How does group-based authorization with GitHub teams currently work in the 2i2c JupyterHub infra? Can you point out the auth flow implementation that our VEDA solution would need to plug into?

@lahirujayathilake
Copy link
Collaborator

@j08lue, I believe we need a third requirement to disable the group after the workshop

@j08lue
Copy link
Collaborator Author

j08lue commented Nov 1, 2024

we need a third requirement to disable the group after the workshop

Thanks, yes! I added one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants