Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Google Authenticator does not use client id from config only env

See original GitHub issue

Putting the setting c.GoogleOAuthAuthenticator.client_id = '...' in the JupyterHub config file results in a redirect to https://accounts.google.com/o/oauth2/v2/auth?redirect_uri=https%3A%2F%2Fexample.com%3A8000%2Fhub%2Foauth_callback&client_id=&response_type=code&state=[secret]&scope=openid+email when logging in. Notice that the client_id is empty. Google properly says something went wrong and that no client ID is provided.

However, if the environmental variable is used instead like

OAUTH_CLIENT_ID=... jupyterhub

Then it works just fine. All other settings are still in config file.

Issue Analytics

State:
Created 5 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

coderforlifecommented, Sep 17, 2018

Okay, so this turned out to be an issue of mine and mine alone. I misspelled GoogleOAuthenticator… I think I need to submit a feature request to traitlets for a warning in debug mode that mentions un-used values or bad names of things…

0reactions

betatimcommented, Sep 18, 2018

No worries. Glad you figured it out 😃

An option in traitlets to warn about unconsumed or likely to be mispelt names would be nice.