[twitter-dev] Twitter Oauth deny access callback bug
I have been using twitter oauth to get access token to use with my app for a year now. It seems that twitter has changed the flow when the user successfully logs in and denies access to the app. Here the user is presented three options. You've denied APP access to interact with your account. APP can not access your Twitter account. 1) Return to APP 2) Go to Twitter. 3) Go to the APP homepage When I click on the first option twitter issues a callback CALLBACK_URL?denied=a_valuedenied=a_value the callback has two parameters with the same name and value ?? This seems to be a bug. We are passing the oauth_token (optional) as a state parameter and this needs to be passed back if the callback is implemented when the user denies app. If this is not a bug please point us to the documentation on how to interpret the two parameters in the callback Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter OAuth Api Freelance Position
Looking for a Twitter API specialist. You MUST have examples of previous work integrating Twitter OAuth into a LAMP based web application. Specifically we are looking for someone who can take an existing Oauth integration and add additional features included the ability to follow users, retweet, and several other features which require credential validation. PLEASE DO NOT APPLY IF YOU DO NOT MEET THE FOLLOWING CREDENTIALS AS YOUR APPLICATION WILL BE IMMEDIATELY DELETED. THANK YOU. -US BASED -ENGLISH SPEAKING -TWITTER OAUTH EXPERIENCE -WORK EXAMPLES -REFERENCES Payment will be made via Paypal - 50% upfront 50% upon completion. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter OAuth Request Token after Facebook Connect - Double login?
Hi I'm trying to setup my site to where a user can connect their Facebook and Twitter accounts. I'm running into a problem where if a user connects Facebook first then Twitter second the request_token I get from $tok = $this-_tw- getRequestToken(); doesn't match the token Twitter sends back after the user confirms my app. Is this a simple session mix up? Or am I doing something wrong? For the first step should I be getting a fresh request token and authorization URL each time is refreshed or should I store them in a session variable to be used? If people click the connect Twitter first instead of Facebook it works smoothly. I know I probably made this really confusing. Please let me know if you need to see/know any of the coding. P.s. I'm using PHP -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter-oAuth-IPhone : Which function on Login Success : twits of followings
Hi All
I am using Twitter-oAuth-IPhone
https://github.com/bengottlieb/Twitter-OAuth-iPhone
Login using this code
if(![twitterObj isAuthorized]){
UIViewController *controller = [SA_OAuthTwitterController
controllerToEnterCredentialsWithTwitterEngine:twitterObj
delegate:self];
NSLog(@twitter 1);
if (controller){
NSLog(@twitter 2);
[[self objectForKey:@self] presentModalViewController:
controller animated: YES];
}
}
I have 2 questions
- I want to do some code on login success and login fail in which
function should I code
- Which function return me the my home page updates i.e twits of
followings
*Amit Battan*
--
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
[twitter-dev] Twitter OAuth 401 Unauthorized
Hello, I am trying to build an application for twitter and in order to do that i need to build functions that post all requests to twitter only with pure PHP. no OAuth libraries or other user build libraries. problem is i always get the 401 unauthorized header. I have done twitter tutorial about this with theyr values(keys) and got same signature base and signature and everything else but when i input my data(secret key and stuff) all i get is 401 unauthorized This is a sample of my sent/received headers POST /oauth/request_token HTTP/1.1 Host:api.twitter.com:443 Content-Type: application/x-www-form-urlencoded Authorization:OAuth oauth_callback=http%3A%2F%2Fadme.ro %2Ftwitter_request.php,oauth_consumer_key=xxx..xxx,oauth_nonce=1299752712,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1299752712,oauth_version=1.0,signature=Mv2IRkcgCp3BNocBKFq8FJNN1OE %3D HTTP/1.1 401 Unauthorized Date: Thu, 10 Mar 2011 10:25:18 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1299752718-94070-29343 Last-Modified: Thu, 10 Mar 2011 10:25:18 GMT X-Runtime: 0.00653 Content-Type: text/html; charset=utf-8 Content-Length: 44 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: k=93.114.42.59.1299752718223070; path=/; expires=Thu, 17- Mar-11 10:25:18 GMT; domain=.twitter.com Set-Cookie: guest_id=129975271823092185; path=/; expires=Sat, 09 Apr 2011 10:25:18 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJePTJ8uAToHaWQiJTYwOGViZTRmYjYzY2Rm %250AYTI5NjM3NDRmZTNkODIwODg3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- c237f0c52f06bd5e58f547db67136857e092fa2f; domain=.twitter.com; path=/; HttpOnly Vary: Accept-Encoding Connection: close Failed to validate oauth signature and token Can someone help me with this? i ran out of ideeas ... -- 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
[twitter-dev] Twitter oAuth in flex
Hello, im getting pretty stuck with trying use oAuth with flex/action script. I was wondering if anyone could help? Cheers -- 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
[twitter-dev] Twitter OAuth PHP - Submit tweets without user login?
I'm using the Twitter OAuth API to try and submit tweets from my site's code. I have the example up and running on localhost and everything works great and I can submit tweets but it goes through a login stage first. Is there a way to bypass this? Basically I just want to tweet to my account using my Twitter account (no user login). The problem seems to be the authentication where it develops a token from the manual login and then uses that to authenticate and then use the API. https://github.com/abraham/twitteroauth/blob/master/DOCUMENTATION How could you do this manually? -- 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
Re: [twitter-dev] Twitter OAuth PHP - Submit tweets without user login?
Use the 'My Access Token' provided in your App page at http://dev.twitter.com which will negate the need to go through the OAuth dance. Scott. On 17 Feb 2011, at 17:25, Adamantus wrote: I'm using the Twitter OAuth API to try and submit tweets from my site's code. I have the example up and running on localhost and everything works great and I can submit tweets but it goes through a login stage first. Is there a way to bypass this? Basically I just want to tweet to my account using my Twitter account (no user login). The problem seems to be the authentication where it develops a token from the manual login and then uses that to authenticate and then use the API. https://github.com/abraham/twitteroauth/blob/master/DOCUMENTATION How could you do this manually? -- 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 -- 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
[twitter-dev] Twitter Oauth and Coldfusion
Can anybody see why the following authorization header would return a 401 when trying to get a request token? OAuth oauth_signature=UlAaUlR5A5uJfCcz%2FUVJl53aRy4%3D, oauth_timestamp=1292450596, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_consumer_key=w50vPfRyCVgzBxtdAsoxwg, oauth_nonce=OAUTH389651810F52376E300436587FC78694 I have tried testing using the netflix oauth tester and that also fails with a 401 -- 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
Re: [twitter-dev] Twitter Oauth and Coldfusion
@Taylor: This isn't the API itself, this is OAuth. request_token is definitely two-legged @Steven: Your header looks fine, the values are properly URL encoded and the time appears to be valid. To help you debug this issue, we need to know the Base String you are testing with, the request you are making (URL, query parameters and post body) and the error code (401 Unauthorized isn't the only 401 code). Tom On 12/15/10 11:23 PM, Taylor Singletary wrote: Hi Steven, I don't see an oauth_token in this header -- all authentication-requiring OAuth-based requests with the Twitter API are 3-legged and require an oauth_token to represent the user. Taylor On Wed, Dec 15, 2010 at 2:11 PM, Steven Neiland steven.sterlingmarket...@gmail.com mailto:steven.sterlingmarket...@gmail.com wrote: Can anybody see why the following authorization header would return a 401 when trying to get a request token? OAuth oauth_signature=UlAaUlR5A5uJfCcz%2FUVJl53aRy4%3D, oauth_timestamp=1292450596, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_consumer_key=w50vPfRyCVgzBxtdAsoxwg, oauth_nonce=OAUTH389651810F52376E300436587FC78694 I have tried testing using the netflix oauth tester and that also fails with a 401 -- 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 -- 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 x -- 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
[twitter-dev] Twitter OAuth replays Blackberry devices in lower case
I am using Twitter OAuth in one of our sites. The oauth_token and oauth_verifier we get from twitter are all mixed cases for all browsers except blackberry browser (blackberry storm). It seems like twitter detects client devices and converts everything to lower case for blackberry. Any ideal? -- 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
[twitter-dev] Twitter OAuth on Wampserver
Is it possible to use Wampserver to test OAuth? I can get basic OAuth to work on-line (on a real domain) but I can only debug PHP on my local Windows computer using Wampserver. At the moment, I can't see how to Register an Application, because the domain name only exists on my local computer, I get Not a valid URL format for domain names like http://localhost -- 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
Re: [twitter-dev] Twitter OAuth on Wampserver
you can use command line oauth with access tokens on a per user basis. On Nov 26, 2010, at 9:01 AM, computergenius wrote: Is it possible to use Wampserver to test OAuth? I can get basic OAuth to work on-line (on a real domain) but I can only debug PHP on my local Windows computer using Wampserver. At the moment, I can't see how to Register an Application, because the domain name only exists on my local computer, I get Not a valid URL format for domain names like http://localhost -- 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 Regards, Edward Hotchkiss edw...@edwardhotchkiss.com http://www.edwardhotchkiss.com/ -- 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
[twitter-dev] Twitter Oauth problem
Hi, My twitter application is Rails based and it uses twitter-auth-0.1.22. The application has been working fine all of the sudden but about a couple weeks ago the app stopped allowing me to sign in via twitter and it displays this message in the log OAuth::Unauthorized (401 Unauthorized): oauth (0.3.5) [v] lib/oauth/consumer.rb:197:in `token_request' oauth (0.3.5) [v] lib/oauth/consumer.rb:125:in `get_request_token' vendor/gems/twitter-auth-0.1.22/app/controllers/ sessions_controller.rb:7:in `new' I haven't change anything and everything including sign in and tweet fetching. The application uses oauth by the way. Any help is appreciated. Many Thanks -- 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
[twitter-dev] twitter oauth :geting undefined index: oauth_token_secret in
Hi am trying to post tweets using oauth (PHP)
i created the application in my twitter account ,
i executed some open source script but that produce the below error,
Notice: Undefined index: oauth_token_secret in
How to fix this issue
my snippet
require_once('twitterOAuth/twitterOAuth.php');
require_once('twitterOAuth/OAuth.php');
$consumer_key='q3fsdfsdfsdw';
$consumer_secret='rfsdfsdfsdfsdfdsfsdL';
$request_token='http://twitter.com/oauth/request_token';
$request_token_secret='5454545';
$oauth = new TwitterOAuth($consumer_key, $consumer_secret,
$request_token, $request_token_secret);
// Ask Twitter for an access token (and an access token secret)
$request = $oauth-getAccessToken();
$access_token = $request['amp;oauth_token'];
$access_token_secret = $request['oauth_token_secret'];=== HERE AM
GETTING TROUBLE
function getAccessToken($token = NULL, $pin = NULL)
{
if ($pin)
$r = $this-oAuthRequest($this-accessTokenURL(),
array(oauth_verifier = $pin));
else
$r = $this-oAuthRequest($this-accessTokenURL());
$token = $this-oAuthParseResponse($r);
$this-token = new OAuthConsumer($token['oauth_token'],
$token['oauth_token_secret']);
return $token;
}
My complete Error Here
Notice: Undefined index: oauth_token_secret in E:\wamp\www\source\oauth
\twitterOAuth\twitteroauth.php on line 118
Notice: Undefined index: oauth_token_secret in E:\wamp\www\source\oauth
\bharani.php
--
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
[twitter-dev] twitter oauth command line
Hi All, I am using the following example in my django app to store users outhtoken into the db. http://github.com/henriklied/django-twitter-oauth But when Iam trying to use the oauth methods through commands http://docs.djangoproject.com/en/dev/howto/custom-management-commands/ it keeps giving me error. AttributeError: 'module' object has no attribute 'OAuthConsumer' Is there any other way to use oauth through command line? thanks for any help ashy -- 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
[twitter-dev] Twitter Oauth Realization within an SAP CRM system
Hello Dev, - We are creating Twitter demo from a SAP CRM system. - With basic authentication everything worked fine. - Now we tried to create an own OAuth client for Twitter with SAP’s programming language ABAP. - We have registered the following (browser) application: http://dev.twitter.com/apps/232392 - Our Twitter user is PC4U. - We could use our OAuth client implementation to a) get access token and secret using the Out-of- band/PIN Code Authentication (oob) process. b) authenticate a simple GET request like http://api.twitter.com/1/statuses/user_timeline.xml. - But when we want to post a message “test” with API http://api.twitter.com/1/statuses/update.xml, it does not work The request is as follows: POST: Content type: application/x-www-form-urlencoded Request body: status=test Authorization Header: OAuth oauth_consumer_key=kpjEiXXXWJnObvdXXXA,oauth_token=1521- L9XXJRAXXXrmcEKZ2JOpLJesteIXXXWtV2LDXXXZD,oauth_timestamp=1285505230,oauth_nonce=2C8ED6FE5D91C4C4AC62CA89269D6DC1,oauth_version=1.0,oauth_signature_method=HMAC- SHA1,oauth_signature=Mh1XX%2Bd4F4XXXAjL3zAb7k4XXXE%3D where… Base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3jEiLXXXJnObvXXXpA%26oauth_nonce %3D2C8ED6FE5DC4AC62CA89269XXX1%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285505230%26oauth_token%3D15258921- L9GT0HrmcEKZ2JOpLJesteIVipWt7BmZD%26oauth_version %3D1.0%26status%3Dtest Key: 3t44BXXwwBc7ghXXXh2wu8bqgtpcrf8igYYYDCsof0IhI8cakKsrXXXCMMJ0lOj7LQ8vkSXmBtKKKaXdw Resulting signature: MhXXd+d4F4ADuAjLXXAb7k4XXXE= Can you please help us fixing this ? Please note that the keys has been masked for security purpose. Regards, Anand -- 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
Re: [twitter-dev] Twitter Oauth Realization within an SAP CRM system
Hi, The Base String looks fine, so does the Authorization header and the signature. What is the error you get back? Not just the error number (probably 401), but also the message. Tom On Mon, 27 Sep 2010 02:34:06 -0700 (PDT), Andyiz mailanand@gmail.com wrote: Hello Dev, - We are creating Twitter demo from a SAP CRM system. - With basic authentication everything worked fine. - Now we tried to create an own OAuth client for Twitter with SAP’s programming language ABAP. - We have registered the following (browser) application: http://dev.twitter.com/apps/232392 - Our Twitter user is PC4U. - We could use our OAuth client implementation to a) get access token and secret using the Out-of- band/PIN Code Authentication (oob) process. b) authenticate a simple GET request like http://api.twitter.com/1/statuses/user_timeline.xml. - But when we want to post a message “test” with API http://api.twitter.com/1/statuses/update.xml, it does not work The request is as follows: POST: Content type: application/x-www-form-urlencoded Request body: status=test Authorization Header: OAuth oauth_consumer_key=kpjEiXXXWJnObvdXXXA,oauth_token=1521- L9XXJRAXXXrmcEKZ2JOpLJesteIXXXWtV2LDXXXZD,oauth_timestamp=1285505230,oauth_nonce=2C8ED6FE5D91C4C4AC62CA89269D6DC1,oauth_version=1.0,oauth_signature_method=HMAC- SHA1,oauth_signature=Mh1XX%2Bd4F4XXXAjL3zAb7k4XXXE%3D where… Base string: POSThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xmloauth_consumer_key%3jEiLXXXJnObvXXXpA%26oauth_nonce %3D2C8ED6FE5DC4AC62CA89269XXX1%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285505230%26oauth_token%3D15258921- L9GT0HrmcEKZ2JOpLJesteIVipWt7BmZD%26oauth_version %3D1.0%26status%3Dtest Key: 3t44BXXwwBc7ghXXXh2wu8bqgtpcrf8igYYYDCsof0IhI8cakKsrXXXCMMJ0lOj7LQ8vkSXmBtKKKaXdw Resulting signature: MhXXd+d4F4ADuAjLXXAb7k4XXXE= Can you please help us fixing this ? Please note that the keys has been masked for security purpose. Regards, Anand -- 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
Re: [twitter-dev] twitter oAuth 401 Unauthorizd error
made callbackurl =oob, it worked! thanks! On Thu, Sep 23, 2010 at 12:57 AM, Tom van der Woerdt i...@tvdw.eu wrote: There's an oauth_callback in your Base String but not in your POST/Authorization header. Tom On 9/23/10 3:00 AM, bill wrote: I have been working on a 401 error from twitter oAuth, but I have no clue. Please see if you can help me Thanks Log === debug: token is now: debug: token_secret is now: debug: Getting request token from http://twitter.com/oauth/request_token debug: callback: debug: signing request with: HMAC-SHA1 debug: Signing with base string: POSThttp%3A%2F%2Ftwitter.com%2Foauth %2Frequest_tokenoauth_callback%3D%26oauth_consumer_key %3D**%26oauth_nonce %3D%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285202944%26oauth_version%3D1.0 debug: Signing with key: * debug: * Connected to tcp://twitter.com:80 debug: POST /oauth/request_token HTTP/1.1 debug: User-Agent: HTTP_Request2/0.5.2 (http://pear.php.net/package/ http_request2) PHP/5.3.1 debug: Authorization: OAuth realm=http://twitter.com/;, oauth_consumer_key=**, oauth_nonce=, oauth_signature=*%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1285202944, oauth_version=1.0 debug: Host: twitter.com debug: Accept-Encoding: gzip, deflate debug: Content-Length: 0 debug: debug: HTTP/1.1 401 Unauthorized debug: date: Thu, 23 Sep 2010 00:49:04 GMT debug: server: hi debug: status: 401 Unauthorized debug: x-transaction: 1285202944-71537-9675 debug: last-modified: Thu, 23 Sep 2010 00:49:04 GMT debug: x-runtime: 0.00586 debug: content-type: text/html; charset=utf-8 debug: pragma: no-cache debug: x-revision: DEV debug: expires: Tue, 31 Mar 1981 05:00:00 GMT debug: cache-control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 debug: x-xss-protection: 1; mode=block debug: x-frame-options: SAMEORIGIN debug: vary: Accept-Encoding debug: content-encoding: gzip debug: content-length: 62 debug: connection: close debug: debug: Failed to validate oauth signature and token debug: * Disconnected Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = / oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) --- In exception block ---ERROR: Failed getting token and token secret from response -- 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 -- 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
Re: [twitter-dev] twitter oAuth 401 Unauthorizd error
Also, please note that OAuth URLs should be https://api.twitter.com/oauth/request_token, https://api.twitter.com/oauth/authorize, and https://api.twitter.com/oauth/access_token. Likewise, API request should go to http://api.twitter.com/1/* Taylor On Wed, Sep 22, 2010 at 10:57 PM, Tom van der Woerdt i...@tvdw.eu wrote: There's an oauth_callback in your Base String but not in your POST/Authorization header. Tom On 9/23/10 3:00 AM, bill wrote: I have been working on a 401 error from twitter oAuth, but I have no clue. Please see if you can help me Thanks Log === debug: token is now: debug: token_secret is now: debug: Getting request token from http://twitter.com/oauth/request_token debug: callback: debug: signing request with: HMAC-SHA1 debug: Signing with base string: POSThttp%3A%2F%2Ftwitter.com%2Foauth %2Frequest_tokenoauth_callback%3D%26oauth_consumer_key %3D**%26oauth_nonce %3D%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285202944%26oauth_version%3D1.0 debug: Signing with key: * debug: * Connected to tcp://twitter.com:80 debug: POST /oauth/request_token HTTP/1.1 debug: User-Agent: HTTP_Request2/0.5.2 (http://pear.php.net/package/ http_request2) PHP/5.3.1 debug: Authorization: OAuth realm=http://twitter.com/;, oauth_consumer_key=**, oauth_nonce=, oauth_signature=*%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1285202944, oauth_version=1.0 debug: Host: twitter.com debug: Accept-Encoding: gzip, deflate debug: Content-Length: 0 debug: debug: HTTP/1.1 401 Unauthorized debug: date: Thu, 23 Sep 2010 00:49:04 GMT debug: server: hi debug: status: 401 Unauthorized debug: x-transaction: 1285202944-71537-9675 debug: last-modified: Thu, 23 Sep 2010 00:49:04 GMT debug: x-runtime: 0.00586 debug: content-type: text/html; charset=utf-8 debug: pragma: no-cache debug: x-revision: DEV debug: expires: Tue, 31 Mar 1981 05:00:00 GMT debug: cache-control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 debug: x-xss-protection: 1; mode=block debug: x-frame-options: SAMEORIGIN debug: vary: Accept-Encoding debug: content-encoding: gzip debug: content-length: 62 debug: connection: close debug: debug: Failed to validate oauth signature and token debug: * Disconnected Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = / oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) --- In exception block ---ERROR: Failed getting token and token secret from response -- 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 -- 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
[twitter-dev] twitter oAuth 401 Unauthorizd error
I have been working on a 401 error from twitter oAuth, but I have no clue. Please see if you can help me Thanks Log === debug: token is now: debug: token_secret is now: debug: Getting request token from http://twitter.com/oauth/request_token debug: callback: debug: signing request with: HMAC-SHA1 debug: Signing with base string: POSThttp%3A%2F%2Ftwitter.com%2Foauth %2Frequest_tokenoauth_callback%3D%26oauth_consumer_key %3D**%26oauth_nonce %3D%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285202944%26oauth_version%3D1.0 debug: Signing with key: * debug: * Connected to tcp://twitter.com:80 debug: POST /oauth/request_token HTTP/1.1 debug: User-Agent: HTTP_Request2/0.5.2 (http://pear.php.net/package/ http_request2) PHP/5.3.1 debug: Authorization: OAuth realm=http://twitter.com/;, oauth_consumer_key=**, oauth_nonce=, oauth_signature=*%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1285202944, oauth_version=1.0 debug: Host: twitter.com debug: Accept-Encoding: gzip, deflate debug: Content-Length: 0 debug: debug: HTTP/1.1 401 Unauthorized debug: date: Thu, 23 Sep 2010 00:49:04 GMT debug: server: hi debug: status: 401 Unauthorized debug: x-transaction: 1285202944-71537-9675 debug: last-modified: Thu, 23 Sep 2010 00:49:04 GMT debug: x-runtime: 0.00586 debug: content-type: text/html; charset=utf-8 debug: pragma: no-cache debug: x-revision: DEV debug: expires: Tue, 31 Mar 1981 05:00:00 GMT debug: cache-control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 debug: x-xss-protection: 1; mode=block debug: x-frame-options: SAMEORIGIN debug: vary: Accept-Encoding debug: content-encoding: gzip debug: content-length: 62 debug: connection: close debug: debug: Failed to validate oauth signature and token debug: * Disconnected Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = / oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) --- In exception block ---ERROR: Failed getting token and token secret from response -- 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] twitter oAuth 401 Unauthorizd error
There's an oauth_callback in your Base String but not in your POST/Authorization header. Tom On 9/23/10 3:00 AM, bill wrote: I have been working on a 401 error from twitter oAuth, but I have no clue. Please see if you can help me Thanks Log === debug: token is now: debug: token_secret is now: debug: Getting request token from http://twitter.com/oauth/request_token debug: callback: debug: signing request with: HMAC-SHA1 debug: Signing with base string: POSThttp%3A%2F%2Ftwitter.com%2Foauth %2Frequest_tokenoauth_callback%3D%26oauth_consumer_key %3D**%26oauth_nonce %3D%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1285202944%26oauth_version%3D1.0 debug: Signing with key: * debug: * Connected to tcp://twitter.com:80 debug: POST /oauth/request_token HTTP/1.1 debug: User-Agent: HTTP_Request2/0.5.2 (http://pear.php.net/package/ http_request2) PHP/5.3.1 debug: Authorization: OAuth realm=http://twitter.com/;, oauth_consumer_key=**, oauth_nonce=, oauth_signature=*%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1285202944, oauth_version=1.0 debug: Host: twitter.com debug: Accept-Encoding: gzip, deflate debug: Content-Length: 0 debug: debug: HTTP/1.1 401 Unauthorized debug: date: Thu, 23 Sep 2010 00:49:04 GMT debug: server: hi debug: status: 401 Unauthorized debug: x-transaction: 1285202944-71537-9675 debug: last-modified: Thu, 23 Sep 2010 00:49:04 GMT debug: x-runtime: 0.00586 debug: content-type: text/html; charset=utf-8 debug: pragma: no-cache debug: x-revision: DEV debug: expires: Tue, 31 Mar 1981 05:00:00 GMT debug: cache-control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 debug: x-xss-protection: 1; mode=block debug: x-frame-options: SAMEORIGIN debug: vary: Accept-Encoding debug: content-encoding: gzip debug: content-length: 62 debug: connection: close debug: debug: Failed to validate oauth signature and token debug: * Disconnected Net_URL2 Object ( [_options:Net_URL2:private] = Array ( [strict] = 1 [use_brackets] = 1 [encode_keys] = 1 [input_separator] = [output_separator] = ) [_scheme:Net_URL2:private] = http [_userinfo:Net_URL2:private] = [_host:Net_URL2:private] = twitter.com [_port:Net_URL2:private] = [_path:Net_URL2:private] = / oauth/request_token [_query:Net_URL2:private] = [_fragment:Net_URL2:private] = ) --- In exception block ---ERROR: Failed getting token and token secret from response -- 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
[twitter-dev] Twitter oAuth file not return token
Hello sir i am authenticate to twitter with my website .first this file was hosted at my old server and better running and return token id but i have shifted to my new server these file now it is not returning token id ,I dont know what is difference in my php.ini and which is disabled .Please help me how to resolve this problem. Thanks Aasim Afridi -- 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] Twitter oAuth file not return token
Are you saying that on your old server you were able to negotiate for a request token on the api.twitter.com/oauth/request_token step but now on your new server you cannot? I would check the server time on your new server, to determine if it is in sync with an NTP time server, or otherwise adjust the clock on demand when generating an oauth_timestamp to +/- 5 minutes of Twitter's server time. Our server time is returned in the Date HTTP header of every request. Thanks, Taylor On Thu, Sep 9, 2010 at 2:37 AM, Choonu aasim.afridi107...@gmail.com wrote: Hello sir i am authenticate to twitter with my website .first this file was hosted at my old server and better running and return token id but i have shifted to my new server these file now it is not returning token id ,I dont know what is difference in my php.ini and which is disabled .Please help me how to resolve this problem. Thanks Aasim Afridi -- 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
[twitter-dev] twitter oauth incredibly slow?
Yesterday I implemented Twitter oAuth on my site, using really nothing but a cut and paste of the example from the twitteroauth class on github. It's working fine, with one hang-up- it's incredibly slow - like at least 30 seconds to process the connection, even during those occasional instances that Twitter itself overall is running fast. See here: http://www.famousquotesabout.com/widget-apps/ I've noticed that other Twitter web apps I've used seem to be able to process the whole interaction, callback and all, in just a couple seconds. I really have no idea what could cause such a delay, and I'm again using really nothing but the bare example code. Has anyone else seen similar issues? -- 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] twitter oauth incredibly slow?
This is definitely not how TwitterOAuth should be acting. You can try the example site and it is running fine: http://twitteroauth.labs.poseurtech.com/connect.php Somethings to check for: Are there an for/while/etc loops in your script that might not be functioning properly? Is it possible that there is code somewhere that is waiting for a period of time? Have to broken down the different parts of the OAuth flow to see if a particular part is slow? Could just your connection to twitter.com from your server be slow? Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sat, Sep 4, 2010 at 08:23, Corey Northcutt corey.northc...@gmail.comwrote: Yesterday I implemented Twitter oAuth on my site, using really nothing but a cut and paste of the example from the twitteroauth class on github. It's working fine, with one hang-up- it's incredibly slow - like at least 30 seconds to process the connection, even during those occasional instances that Twitter itself overall is running fast. See here: http://www.famousquotesabout.com/widget-apps/ I've noticed that other Twitter web apps I've used seem to be able to process the whole interaction, callback and all, in just a couple seconds. I really have no idea what could cause such a delay, and I'm again using really nothing but the bare example code. Has anyone else seen similar issues? -- 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] Twitter oAuth
Thanks. BTW, basic auth seems still available on some applications (e.g., http://twtkr.com/index.php ). I just wondered whether there is a way to verify id/password via OAuth. On Thu, Sep 2, 2010 at 6:10 AM, Matt Harris thematthar...@twitter.com wrote: Hey Edward, Basic Auth on the REST API was disabled August 31st. All authenticated requests to the REST API (anything on http://api.twitter.com) need to use OAuth. There is more information on our developer resources site: http://dev.twitter.com/pages/basic_to_oauth Hope that helps, Matt On Tue, Aug 31, 2010 at 8:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Is it still possible to login using username/password? then, how can I program it? -- Best Regards, Edward J. Yoon edwardy...@apache.org http://blog.udanax.org -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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 -- Best Regards, Edward J. Yoon edwardy...@apache.org http://blog.udanax.org -- 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] Twitter oAuth
BTW, basic auth seems still available on some applications (e.g., http://twtkr.com/index.php ). I just wondered whether there is a way to verify id/password via OAuth. Those apps are probably using xAuth. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Diamonds are forever. -- -- 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] Twitter oAuth
Thanks! On Thu, Sep 2, 2010 at 10:56 PM, Cameron Kaiser spec...@floodgap.com wrote: BTW, basic auth seems still available on some applications (e.g., http://twtkr.com/index.php ). I just wondered whether there is a way to verify id/password via OAuth. Those apps are probably using xAuth. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Diamonds are forever. -- -- 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 -- Best Regards, Edward J. Yoon edwardy...@apache.org http://blog.udanax.org -- 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] Twitter oAuth
Hey Edward, Basic Auth on the REST API was disabled August 31st. All authenticated requests to the REST API (anything on http://api.twitter.com) need to use OAuth. There is more information on our developer resources site: http://dev.twitter.com/pages/basic_to_oauth Hope that helps, Matt On Tue, Aug 31, 2010 at 8:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Is it still possible to login using username/password? then, how can I program it? -- Best Regards, Edward J. Yoon edwardy...@apache.org http://blog.udanax.org -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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-dev] Twitter OAuth Echo and PHP
I am looking for some help, I am grabbing the full headers from a request sent by the iPhone twitter app to my PHP application. I am looking to grab the username, and well all avail content from https://api.twitter.com/1/account/verify_credentials.json ... I was told OAuth Echo would be the route to take. I am just not clear on how to send the request back to Twitter. I have tried a dozen or so Curl options and also tried to use Abrahams OAuth functions and always get the following Could not authenticate you response back. Can any assist me on how the headers should be sent back to get a correct response? thanks a million in advance. -- 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-dev] Twitter oAuth
Is it still possible to login using username/password? then, how can I program it? -- Best Regards, Edward J. Yoon edwardy...@apache.org http://blog.udanax.org -- 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-dev] Twitter OAuth Authentication Fails
I have three iPhone apps that use OAuth to communicate with Twitter. They have been working well for several months but recently when trying to set-up authentication and exchange the various OAuth tokens using Safari on the iPhone, Safari brings up a page from Twitter that says: Something is technically wrong. Thanks for noticing -- we're going to fix it up and have things back to normal soon. Normally authentication works and the page Twitter returns redirects back to our application on the iPhone. Again, this has all worked for several months until very recently. We just noticed the problem ourselves today. Here's an example authenticate URL that used to work but now fails: http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0AZnHkIwg1GfvRn9HaNMB7q0force_login=true Does anyone out there know what's going wrong? This has all worked for hundreds of thousands of our customers for several months now and nothing in our app has changed in two months. Can anyone shed light on this for me? Thanks! -- 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] Twitter OAuth Authentication Fails
Hi Kevin, Thanks for raising this query. We have a fix on it's way out tonight or tomorrow morning for this. Also, whilst this isn't related to the issue you are experiencing I recommended updating your URL to point to our API. All requests for the API should be directed to http://api.twitter.com/1/method. OAuth requests should go to https://api.twitter.com/oauth/method,e.g. https://api.twitter.com/oauth/authenticate Best, Matt On Tue, Aug 24, 2010 at 4:55 PM, Kevin Wallace kevin.wall...@abvio.com wrote: I have three iPhone apps that use OAuth to communicate with Twitter. They have been working well for several months but recently when trying to set-up authentication and exchange the various OAuth tokens using Safari on the iPhone, Safari brings up a page from Twitter that says: Something is technically wrong. Thanks for noticing -- we're going to fix it up and have things back to normal soon. Normally authentication works and the page Twitter returns redirects back to our application on the iPhone. Again, this has all worked for several months until very recently. We just noticed the problem ourselves today. Here's an example authenticate URL that used to work but now fails: http://twitter.com/oauth/authenticate?oauth_token=r8ZW21dPbUteSOgfFJ0AZnHkIwg1GfvRn9HaNMB7q0force_login=true Does anyone out there know what's going wrong? This has all worked for hundreds of thousands of our customers for several months now and nothing in our app has changed in two months. Can anyone shed light on this for me? Thanks! -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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-dev] Twitter OAuth Example?
Hi everyone, could somebody please help me I need a simple Twitter OAuth example that fully running along with the source code I've tried some example that I found in the internet but all of them is not running and the code is in a mess (unreadable) please help me my brothers and sisters :)
[twitter-dev] Twitter oAuth for PHP, some advice needed
Hi Everyone. I've been puzzling over OAuth for some time now with little insight into how to apply it to my situation. If someone could nudge me in the right direction I'd be most grateful. What I am doing now is very simple. Whenever my company publishes new content to it's websites, the company Twitter account is updated to reflect it. This is not an application that is open to public use. It doesn't require any browser-based login boxes or http redirects as part of the process. In fact, such a requirement would prevent the function of my current routine. EXAMPLE: (synopsis) require classes/Twitter.class.php; $PMTtweet = new Twitter($twitterunamePMT, $twitterpwordPMT); $PMTsuccess = $PMTtweet-update($thisTweet); My questions are: 1. Do I need to upgrade to OAuth? 2. If I need to upgrade to OAuth, can it be done in such a way as to work without browser login and redirect requirements? (as per example) 3. If 2 is true, any tutorials that match that situation you can point me to? 4. If 1 2, where/how would I acquire the tokens necessary to use OAuth? Apologies for the basic questions. I really did make an effort to ferret out the answers but all the examples I encountered were much more complex than my situation requires. Thanks Paul G
Re: [twitter-dev] Twitter oAuth for PHP, some advice needed
one quick followup on this, if I may... The Twitter account I registered the app with provided consumer keys / secrets and I used those keys with the client's access tokens to successfully get and post to the account using OAuth. Great. Many thanks to those who pointed me in the right direction. I actually have two separate Twitter accounts to do status updates for depending on the content I have. Sometimes in immediate succession. Is there a way to retrieve the consumer keys for the other Twitter account I own without registering an app? Thank you Paul G
[twitter-dev] Twitter OAuth Problem
Hi, I have been using Abraham's OAuth library and I *almost* have it working. I'm a longtime C++ developer but new to Twitter API. Anyway, it took me a while to use the callback.php file as the actual call back. That (I thought) was the missing element, I was under the impression that the test.php file in his library could be substituted for the callback. Anyway when I realized the mistake I was happy to implement the new code. The new callback is being called but I am consistently getting HTTP Error Code 401 (unauthorized) when it is being used, and I am using it basically as is. Any insight would be appreciated. Note - I did regenerate my application registration recently - how long does it take for those credentials to be usable? Thanks much. -Gabe
[twitter-dev] Twitter Oauth Integration
Hi All, Can you please help me in integrating Oauth to our app , thanks Anilkumar
[twitter-dev] Twitter OAuth Timestamps
I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
RE: [twitter-dev] Twitter OAuth Timestamps
This is known and expected behavior. There have been other threads about it in the last couple of weeks. If you get a 401 response, you should compare the Date header of Twitter's response to the current system time. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Twitter OAuth Timestamps
I'll make this much clearer in the documentation, and also include tips to work around it dynamically. We have a revision of our OAuth implementation that we'll be gradually introducing into the system in the near future. It's going to be opt-in for awhile so that we can work out any kinks, as it's going to be a bit stricter to the spec. The new implementation will have the added benefits of more detailed error messages throughout OAuth authentication and authorization, including better messages as to the reason of the rejected request and signature base strings on signature mis-matches. Thanks, Taylor On Tue, May 25, 2010 at 5:49 PM, Brian Smith br...@briansmith.org wrote: This is known and expected behavior. There have been other threads about it in the last couple of weeks. If you get a 401 response, you should compare the Date header of Twitter's response to the current system time. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here: http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Twitter OAuth Timestamps
On Tue, 25 May 2010 19:49:28 -0500 Brian Smith br...@briansmith.org wrote: This is known and expected behavior. There have been other threads about it in the last couple of weeks. If you get a 401 response, you should compare the Date header of Twitter's response to the current system time. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian I am seeing headers coming back from twitter with Expires : Tue, 31 Mar 1981 05:00:00 GMT on replies with good status. Nothing going wrong, auth works fine. Just a funny looking date in there. Is that sombody's epoch? It looks vaguely familiar. -- Bernd Stramm bernd.str...@gmail.com
Re: [twitter-dev] twitter oauth
For those of us who use simple Classic ASP scripts and Xhttp to autmatically update statuses for our websites (my site automatically updates its twitter status whenever someone posts a new ad), or for those who use PHP curl for similar things, why not bypass Oauth altogether, and instead of deprecating basic authentication altogether, make a few minor changes to it for our needs? Have us go ahead and register our app with twitter, or the URL which bears the code to send the twitter update. Have twitter issue a key and secret for that url. Have twitter check to make sure the url sending an update is a registered app and that it has the correct key and secret . If/when 2 legged oauth is activated, will it work that way?
[twitter-dev] twitter oauth
hello one questionn ,, i can have a oauth authentication in web browse and app desktop the same time ... why the methos are diferents thanks in advance
Re: [twitter-dev] twitter oauth
On 4/28/2010 4:15 PM, nav wrote: hello one questionn ,, i can have a oauth authentication in web browse and app desktop the same time ... why the methos are diferents thanks in advance The methods are different because the targets are different. With a web application, you are sending the client to twitter from you web site, and twitter can send the client back to you with the oAuth data. With a local desktop, on the other hand, you can not redirect the user as easily. So in place, the user receives a PIN that they can input into the oAuth desktop app and then the app can use to get the access tokens. HTH.
[twitter-dev] Twitter OAuth fails
Hello, I am using abraham's twitter OAuth PHP library to build a basic application and it is failing. It is failing at: $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET); /* Get request token */ $request_token = $connection-getRequestToken(OAUTH_CALLBACK); The returned http_code is 0. I have registered my application with a valid callback URL and have got a consumer and a secret key which I am using it in the code. Let me know if I am missing anything. Thanks in Advance.
[twitter-dev] Twitter Oauth Issues
Hello folks, I'm developing a twitter desktop client for windows using the Oauth method, but for some reason I'm getting this error while requesting an Access token The remote server returned an error: (401) Unauthorized.. This issue is only happening in my development PC, I've tried the app in other computers and Internet Connections and it works great, I'm guessing this is happening because I make too much requests to twitter from the same computer. Could anyone help me on this issue ? Thanks.
Re: [twitter-dev] Twitter Oauth Issues
Server timestamp difference? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Jan 13, 2010 at 4:16 PM, Proxdeveloper prox.develo...@gmail.com wrote: Hello folks, I'm developing a twitter desktop client for windows using the Oauth method, but for some reason I'm getting this error while requesting an Access token The remote server returned an error: (401) Unauthorized.. This issue is only happening in my development PC, I've tried the app in other computers and Internet Connections and it works great, I'm guessing this is happening because I make too much requests to twitter from the same computer. Could anyone help me on this issue ? Thanks.
[twitter-dev] Twitter OAuth works fine in my app then I get error when trying to login to Twitter.com site
OAuth works fine in my application but then when I open a new tab to login to twitter, I login and I get this message: Woah there! This page requires some information that was not provided. Please return to the site that sent you to this page and try again … it was probably an honest mistake. When I hit back on the browser, the error message goes away and I am at my home page. This looks to be a bug with Twitter's OAuth. Here are the steps to reproduce: 1) Make sure you are logged out of twitter.com 2) Use a third party app to login to twitter: (you can use this demo: http://twitteroauth.appspot.com/) 3) Open a second tab, go to twitter.com and login. You should get the error message above? I am not too familiar with OAuth but I have used a few different code libraries for python and they all seem to have the same issue. Any one experience similar?
Re: [twitter-dev] Twitter OAuth works fine in my app then I get error when trying to login to Twitter.com site
Following up to myself: Yes I experience the same. Not sure what causes it... I see the same thing. The browser location bar shows http://twitter.com/oauth/authorize when you have the error page up. So something is redirecting us to the /oauth when we try a normal web login. Digging a little, I see a twitter.com _twitter_sess cookie is pushed to my browser by Twitter when I'm redirected to the auth page in step 2. The cookie is set to expire at end of session. Maybe that should be changed to have it expire in a couple of minutes, or maybe that cookie shouldn't be pushed to us at all. Does it interfere with signing in with a second 3rd party app? If I remove that cookie before going to Twitter in step 3, it all works fine. 1) Make sure you are logged out of twitter.com 2) Use a third party app to login to twitter 3) Open a second tab, go to twitter.com and login. You should get the error message above? Terry
Re: [twitter-dev] Twitter OAuth works fine in my app then I get error when trying to login to Twitter.com site
There is an issue open for this: http://code.google.com/p/twitter-api/issues/detail?id=1199 Abraham On Sat, Nov 28, 2009 at 14:30, Terry Jones te...@jon.es wrote: Following up to myself: Yes I experience the same. Not sure what causes it... I see the same thing. The browser location bar shows http://twitter.com/oauth/authorize when you have the error page up. So something is redirecting us to the /oauth when we try a normal web login. Digging a little, I see a twitter.com _twitter_sess cookie is pushed to my browser by Twitter when I'm redirected to the auth page in step 2. The cookie is set to expire at end of session. Maybe that should be changed to have it expire in a couple of minutes, or maybe that cookie shouldn't be pushed to us at all. Does it interfere with signing in with a second 3rd party app? If I remove that cookie before going to Twitter in step 3, it all works fine. 1) Make sure you are logged out of twitter.com 2) Use a third party app to login to twitter 3) Open a second tab, go to twitter.com and login. You should get the error message above? Terry -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | Awesome Lists | http://twitterli.st This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Twitter OAuth 'Incorrect Signature' Error in update method, when using special char or space in STATUS
Hi, I'm using Apache HttpPost to update the status. it works fine when using only single word plain text Status message. but fails when entering more than one word or any special char. seems i'm doing something wrong in encoding of status message. please help me nd lemme know what encoding needs before appendibf status in SBS and also in UrL Also, despite using Post, i need to append entire requet param in request URL. if i dont do so, it throw sme incorrect sign error. Thanks in advance!
[twitter-dev] Twitter+Oauth on iPhone: How does one logout?
I'm implementing Twitter+Oauth on the iPhone using http://github.com/bengottlieb/Twitter-OAuth-iPhone. I'm creating a login/logout button/feature like facebook connect uses. I've got the login working and am wondering how does one logout using Oauth?
[twitter-dev] Twitter + OAuth for iPhone
If anyone is interested, I've implemented Twitter OAuth on iPhone (which includes an iPhone version of the OAuth static lib). It's on GitHub: http://github.com/bengottlieb/Twitter-OAuth-iPhone/tree/master
