[twitter-dev] Re: Getting 401 when using one access token with OAuth
Thanks for this response, Taylor. Turns out I was making a noob mistake and it's all squared away. Your trouble shooting tips helped me find that mistake. ~Barry On May 17, 9:58 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Barry, Unfortunately can't go to the logs to figure out what's going wrong -- but happy to help. You don't need xAuth access to get this to work, you are correct. There may be other reasons it is failing for you. One thing to check is that your system clock is synced with a NTP server or reasonably correct -- if the timestamp generated by the OAuth flow doesn't match ours within about 5 minutes, you'll get an invalid request. As for the example: just dotting i's: you've placed your consumer key and secret on line 3 of the example and your oauth_token and oauth_token_secret (access token) on the method call for prepare_access_token? Assuming all is correct, this part should function. After you've checked your clock and if you're still having issues I'll help you debug this further. Thanks, Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Mon, May 17, 2010 at 7:35 AM, bjhess ba...@bjhess.com wrote: I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
[twitter-dev] Re: Getting 401 when using one access token with OAuth
I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
Re: [twitter-dev] Re: Getting 401 when using one access token with OAuth
Hi Barry, Unfortunately can't go to the logs to figure out what's going wrong -- but happy to help. You don't need xAuth access to get this to work, you are correct. There may be other reasons it is failing for you. One thing to check is that your system clock is synced with a NTP server or reasonably correct -- if the timestamp generated by the OAuth flow doesn't match ours within about 5 minutes, you'll get an invalid request. As for the example: just dotting i's: you've placed your consumer key and secret on line 3 of the example and your oauth_token and oauth_token_secret (access token) on the method call for prepare_access_token? Assuming all is correct, this part should function. After you've checked your clock and if you're still having issues I'll help you debug this further. Thanks, Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, May 17, 2010 at 7:35 AM, bjhess ba...@bjhess.com wrote: I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
[twitter-dev] Re: Getting 401 when using one access token with OAuth
Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c04e4f73929a15c3/d9b6ab0c427493eb#d9b6ab0c427493eb regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
