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

Jump to bottom

[P&S Initiative] VEDA Objective JH-5: Move 1 production hub to keycloak (once there is a production deployment) #5413

Open
1 task
jnywong opened this issue Jan 24, 2025 · 0 comments
Open
1 task

[P&S Initiative] VEDA Objective JH-5: Move 1 production hub to keycloak (once there is a production deployment) #5413

jnywong opened this issue Jan 24, 2025 · 0 comments
Labels
external Requires external collaboration

Comments

@jnywong
Copy link
Member

jnywong commented Jan 24, 2025

Motivation

Currently, the JupyterHubs use GitHub for authentication and GitHub groups for Authorization.

Description

Once there’s a production deployment of Keycloak, we should migrate 1 production hub (to be chosen in consultation with Science Support) to Keycloak for both authentication and authorization.

Acceptance Criteria

  • One production JupyterHub is using Keycloak for Authentication and Authorization

Personnel

  • @sunu
  • 2i2c Product & Services Team (in general)
@jnywong jnywong added the external Requires external collaboration label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
external Requires external collaboration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jnywong