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

try generic openid-connect config #605

Merged
merged 1 commit into from
May 12, 2020

Conversation

rabernat
Copy link
Member

After #604 failed, I'm trying a new approach.

Here is secrets/staging.yaml.

pangeo:
  jupyterhub:
    auth:
      custom:
        config:
          client_id: "XXX"
          client_secret: "XXX"

@rabernat
Copy link
Member Author

@rabernat rabernat merged commit 623923c into pangeo-data:staging May 12, 2020
@rabernat
Copy link
Member Author

This deployed successfully, but is not quite working. The auth link is https://staging.hub.pangeo.io/hub/oauth_login?next=

Something must not be set right.

@rabernat
Copy link
Member Author

In the hub log, I'm seeing

[E 2020-05-12 16:53:37.031 JupyterHub generic:144] OAuth user contains no key nickname: {}
[W 2020-05-12 16:53:37.031 JupyterHub base:714] Failed login for unknown user
[W 2020-05-12 16:53:37.033 JupyterHub log:174] 403 GET /hub/oauth_callback?code=[secret]&state=[secret] (@10.128.0.143) 423.83ms

It seems that the oauth user is cached. I'm going to try deleting cookies.

@rabernat
Copy link
Member Author

So after clearing cookies, I was able to log in via auth0. Yay! But then I hit the same error

[E 2020-05-12 17:06:03.515 JupyterHub generic:144] OAuth user contains no key nickname: {}
[W 2020-05-12 17:06:03.516 JupyterHub base:714] Failed login for unknown user

So it seems that we are not getting the proper user data.

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

Successfully merging this pull request may close these issues.

1 participant