From 3bc2ab23792b958ba57e419bfff8dc37979eeb15 Mon Sep 17 00:00:00 2001 From: Georgiana Dolocan Date: Tue, 14 Mar 2023 15:58:01 +0200 Subject: [PATCH] Add instruction about the profile scope needed to get the preferred username claim from GitHub --- docs/hub-deployment-guide/configure-auth/cilogon.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/hub-deployment-guide/configure-auth/cilogon.md b/docs/hub-deployment-guide/configure-auth/cilogon.md index 9d3e04aa17..d77f215f19 100644 --- a/docs/hub-deployment-guide/configure-auth/cilogon.md +++ b/docs/hub-deployment-guide/configure-auth/cilogon.md @@ -129,7 +129,6 @@ The steps to enable the JupyterHub CILogonOAuthenticator for a hub are similar w 3. **Authenticate using GitHub with CILogon**: *This example sets the GitHub nickname as the Hub username using the `username_claim` option* - ```yaml jupyterhub: hub: @@ -137,6 +136,8 @@ The steps to enable the JupyterHub CILogonOAuthenticator for a hub are similar w JupyterHub: authenticator_class: cilogon CILogonOAuthenticator: + scope: + - "profile" oauth_callback_url: https://{{ HUB_DOMAIN }}/hub/oauth_callback shown_idps: - http://github.com/login/oauth/authorize