This will work.
Thanks everyone!
On Apr 4, 5:01 am, "@godspeedelbow" wrote:
> Basically, it is suggested that you store the user's session and pick
> it up again after the oauth sends the user back to your site.
> So the question is: how to uniquely identify the user through the
> callback?
>
>
Basically, it is suggested that you store the user's session and pick
it up again after the oauth sends the user back to your site.
So the question is: how to uniquely identify the user through the
callback?
Sending a variable along to twitter, and hoping it will come back,
apparently doesn't work
Correct, I am trying to pass in a variable and looking for that
variable from the callback to reinitiate my session. I am doing this
because i am not able to retain current user's session.
Currently after the callback from oAuth i lose my users session. So
the user session is set before the oAut
Hey,
I think you might be trying to pass in a variable, and expect the oAuth
callback url to use that variable?
i.e. pass in a clientId of "123" and expect that the url returned will point
to somecallbackurl.com?auth_token_4566&clientId=123
What you want to do is:
a) set a session on your end
b) r
After the callback happens from twitter back to my site, my param is
not included.
I tried both appending a param to the http://twitter.com/oauth/authorize
url
and also my oauth_callback url when redirecing with no success.
Only one querystring returns which is the auth_token from the
callback.
