-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
google oauth 2.0 #20
Comments
Hey, I'm running into the same error here. When I initially authenticate using django-social-auth, I get the refresh_token, but if I remove the authentication and add it back in, there's no refresh_token to be found. Did you run into this too? If so, did you discover the cause? |
According to Google, the |
Thanks! Setting |
I was patched lib (added checking empty refresh_token in google response, and if it empty, not save it to db), it is not very good solution, but I think re-authing user every time, bad idea too.. |
The re-auth is required by google, you talk about another issue which is already solved in python-social-auth. |
After authentication I have in table 'social_auth_usersocialauth' extra_data={"token_type": "Bearer", "access_token": "ya29.AHES6ZQtbhA1K-CmCn8bvnZy.................AgCfk8", "expires": 3599} without refresh_token. I think refresh_token is a required part of response.
The text was updated successfully, but these errors were encountered: