[twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect
I have a sample app which works fine on my local machine. When I deploy it to a dev server and go through the flow, I get the PIN in the browser and no redirect. I checked the server timestamps and they are within 1 second of each other. Does anyone have any thoughts on what might be wrong? I looked through dev.twitter.com oauth pages but I didn't see anything besides the server timestamps. Thanks much! /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect
Hi Damon, Verify that your application has a default callback URL set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into out of band mode or note. Further, while that default callback URL needs to exist on your application record, make sure that you're sending an oauth_callback on the request token step with the URL you want to be directed to following the authentication step -- it's best to be explicit instead of relying on some implicit setting in your application record (and not providing an oauth_callback on the request token step is not correct to the specification). Taylor On Wed, Sep 1, 2010 at 11:26 AM, Damon Clinkscales sca...@pobox.com wrote: I have a sample app which works fine on my local machine. When I deploy it to a dev server and go through the flow, I get the PIN in the browser and no redirect. I checked the server timestamps and they are within 1 second of each other. Does anyone have any thoughts on what might be wrong? I looked through dev.twitter.com oauth pages but I didn't see anything besides the server timestamps. Thanks much! /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect
On Wed, Sep 1, 2010 at 3:25 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Damon, Verify that your application has a default callback URL set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into out of band mode or note. Further, while that default callback URL needs to exist on your application record, make sure that you're sending an oauth_callback on the request token step with the URL you want to be directed to following the authentication step -- it's best to be explicit instead of relying on some implicit setting in your application record (and not providing an oauth_callback on the request token step is not correct to the specification). Taylor Thanks Taylor. Yes, I had figured out that I needed to specify one in the call as well (I had already set one in the dev.twitter.com UI). I don't know the precise cause of the issue, but I did figure out it was a gem version issue. 'oauth' Ruby gem 0.3.4 works and 'oauth' Ruby gem 0.4.2 does not. If anyone can shed any light on that, it'd be much appreciated, but at least 0.3.4 is working. Thanks, /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect
Great. I'll take a look at the most recent version of the ruby gem as soon as I get a chance. From my experience, 0.3.4 was a very solid release. I'll follow up when I've had a chance to review. Thanks, Taylor On Wed, Sep 1, 2010 at 2:38 PM, Damon Clinkscales sca...@pobox.com wrote: On Wed, Sep 1, 2010 at 3:25 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Damon, Verify that your application has a default callback URL set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into out of band mode or note. Further, while that default callback URL needs to exist on your application record, make sure that you're sending an oauth_callback on the request token step with the URL you want to be directed to following the authentication step -- it's best to be explicit instead of relying on some implicit setting in your application record (and not providing an oauth_callback on the request token step is not correct to the specification). Taylor Thanks Taylor. Yes, I had figured out that I needed to specify one in the call as well (I had already set one in the dev.twitter.com UI). I don't know the precise cause of the issue, but I did figure out it was a gem version issue. 'oauth' Ruby gem 0.3.4 works and 'oauth' Ruby gem 0.4.2 does not. If anyone can shed any light on that, it'd be much appreciated, but at least 0.3.4 is working. Thanks, /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
