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

Error returning OAuth user info: missing_token due to AuthLib V1.0.0 #19255

Closed
3 tasks done
JZ6 opened this issue Mar 18, 2022 · 3 comments
Closed
3 tasks done

Error returning OAuth user info: missing_token due to AuthLib V1.0.0 #19255

JZ6 opened this issue Mar 18, 2022 · 3 comments
Labels
#bug Bug report

Comments

@JZ6
Copy link
Contributor

JZ6 commented Mar 18, 2022

The latest AuthLib breaks Oauth, returns the "Error returning OAuth user info: missing_token".
Downgrading back to authlib==0.15.5 fixes this error and allows SSO to work again.

How to reproduce the bug

  1. Setup Google Oauth
  2. Install Authlib 1.0.0
  3. Try to login
  4. See Error returning OAuth user info: missing_token

Expected results

Login via google SSO keeps working.

Actual results

Latest AuthLib releases throws a missing_token error.

Screenshots

If applicable, add screenshots to help explain your problem.
image

Environment

(please complete the following information):

  • browser type and version: Chrome
  • superset version: 1.4.0
  • python version: 3.9.7
  • node.js version: 16.9.0
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@rusackas
Copy link
Member

Is this still an issue on 2.0.1?

@longtomjr
Copy link

I have tested this again. It does not seem to be an issue anymore. Just note that it does not work if using:
'server_metadata_url': 'https://accounts.google.com/.well-known/openid-configuration',

The URLs have to be manually defined.

@rusackas
Copy link
Member

rusackas commented Apr 6, 2023

Thanks @longtomjr!

@rusackas rusackas closed this as completed Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

3 participants