I have a situation where I want to make a third party request INSIDE a current users request.
Essentially I want to alter the traditional oauth2 flow where the user is redirected back to the Application after authorizing their credentials for the first time. I would like the Application to receive the authorization code once the user approves it via an internal Request inside Django. But I want to redirect the user to stay within my site for some additional account process wizards. This is a situation where oath is being used to authorize a third part iOS or Android application, not a browser app so I essentially don't care if the user is redirected to the Application's own post-authorization splash page. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/814ad3c9-752a-476c-9da8-f3eaa499ee31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
