Wagner de Lima

@denizdogan that's alright. The idea is still valid.

@exgphe hope you're doing well. I managed to investigate the issue a little further. I replicated the issue described at: "Same issue as https://github.com/RealmTeam/django-rest-framework-social-oauth2/issues/208" Here is the pipeline: ``` SOCIAL_AUTH_PIPELINE...

@butorov I am currently investigating this issue.

@butorov this guide shows how to create the instagram app. [Getting started](https://developers.facebook.com/docs/instagram-basic-display-api/getting-started) Also, the guide does not include the `redirect_state` param. I removed it and the request worked as expected....

I am closing this issue. You can handle password-based authentication in your backend. It's not drf-social-oauth's responsibility to deal with it, since it already deals with multiple social backend's sign-in.

@MidoCobra @ecakashjadhav @fahedmahidi @bilal-nexquery, If you have a customer user you will need to handle the duplicate email address on your backend. drf-social-oauth2 does not save the email address. Here...

@SukiCZ I made a comment to the other issue regarding github login. Let's get this sorted first then we can talk about reverting the changes from feat/remove-token-duplication.

@futurbotconsolidated I am closing this issue. This seemed like a good idea at first. I have been thinking about this for a while now but I think it would be...

Please, give me more context on what you need to do here. Thanks.

I am closing this issue due to a lack of context.