That text is not done very well. When the users hits the call back_url you still have to make a call to oauth/access_token. That will return the full token, user_id, screen_name.
Abraham On Wed, Jul 22, 2009 at 05:29, CG <learn....@gmail.com> wrote: > > Hi all, I hv this doubt and hope that somebody can help ... > > II hv tried to use Sign-in-with-twitter , and when the user click > allow , it redirects to my Callback URL with only the > ?oauth_token=xxxxxx and no token secret. > > I read the flow of sign-in-with-twitter , it mentioned that "Redirect > back to callback_url, including access token and token secret if > authorized" . In my case, does it mean that authentication failed ? if > yes, how do I know what error is it ? If no , how can I get the > token_secret ? > > > Thanks in advanced for any hints ... > > Cheers, > CG > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
