-
Notifications
You must be signed in to change notification settings - Fork 33
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
Use pipeline and support partial #18
Comments
https://github.com/fivethreeo/django-graphql-social-auth - made a working idea here |
@fivethreeo I've seen the updates to your fork and you seem to have implemented support for setting a Thanks! |
The state part what was made some of the issues that made me think rest or another was a better idea. But if you can find a good solution. That would be great 😀
… 10. mai 2020 kl. 20:35 skrev Andrei Marinescu ***@***.***>:
@fivethreeo I've seen the updates to your fork and you seem to have implemented support for setting a redirect_uri, however I can't seem to get it to work (it's complaining about a missing state parameter that I've seen was commented out). Would you happen to have any pointers in how this might work?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thanks for your reply, this is much appreciated. I was pulling my hair (not much left) for the past 24 hours trying to make this work. Getting social auth, graphene and JWT to work with a React front-end seems to be much harder to achieve than what I thought it would. I did get this to work by using your branch, and I probably wouldn't have been able to otherwise, given the fact I'm quite new to the ecosystem and still learning how python-social-auth works (with all it's different flavors, pardon the pun). The modifications I needed to make were adding the following lines to the
This probably needs more work before being rock solid, but hopefully it helps anyone facing similar issues. |
Maybe using uniontype. I might implement it.
The text was updated successfully, but these errors were encountered: