On the request_token step of the OAuth flow, are you setting an explicit oauth_callback pointing to where you want the user to be redirected after they have authorized?
@episod <http://twitter.com/intent/user?screen_name=episod> - Taylor Singletary On Thu, Jul 14, 2011 at 12:09 AM, Paul <[email protected]> wrote: > Hi, > > Im trying to do a Sign In with Twiter from my site, but im stuck. I've > double checked my application settings (i cant find the application on > the new applications site that specifies if the app is a desktop or > webapp), i've added a callbackurl. > > On my site im getting the correct request token and generate my link > as : https://twitter.com/oauth/authenticate?oauth_token=XXXXXXXXXXXX > (X being the request_token). > > I've i click on the link i get to the twitter authorise page and the > url says authenticate, BUT as soon as I sign in the twitter site gives > me the PIN code and doesnt redirect. From what I understood this url > should be correct. > > What am i doing wrong? > > Thank you. > > -- > Have you visited the Developer Discussions feature on > https://dev.twitter.com/discussions yet? > > Twitter developer links: > Documentation and resources: https://dev.twitter.com/docs > API updates via Twitter: https://twitter.com/twitterapi > > Unsubscribe or change your group membership settings: > http://groups.google.com/group/twitter-development-talk/subscribe > -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
