I am new to Twitter OAuth API.
I am trying to tune a piece of code like this, and I registered a free hosting on 0fees.net, and try to test some code and get familiar with OAuth.
But when I try to get the AuthencatieUrl I get the following error:
Fatal error: Uncaught exception 'EpiOAuthException' in /home/vol3/0fees.net/fees0_6530770/htdocs/Twi/EpiOAuth.php:313 Stack trace: #0 /home/vol3/0fees.net/fees0_6530770/htdocs/Twi/EpiOAuth.php(290): EpiOAuthException::raise(NULL, NULL) #1 /home/vol3/0fees.net/fees0_6530770/htdocs/Twi/EpiOAuth.php(33): EpiOAuthResponse->__get('oauth_token') #2 /home/vol3/0fees.net/fees0_6530770/htdocs/Twi/sign-in.php(15): EpiOAuth->getAuthenticateUrl() #3 {main} thrown in /home/vol3/0fees.net/fees0_6530770/htdocs/Twi/EpiOAuth.php on line 313
I debugged a little bit, it seems that the token request is always null on the free hosting..
But the same code works on my localhost, the token is retrieved right and the AuthencationURL from Twitter is also OK.....but I could not give localhost URL as callback..
Have you guys know this problem?
Thanks & Regards.
Larry.
I had this same problem on my localhost. Changing it to 127.0.0.1 on the URL fixed the problem for me. However I know it doesn't quite answer your question, but anybody coming across this with a similar problem, knowing this tidbit may help. Best
Related
I'm developer working on integration between our product and LinkedIn. It's been decided we use https://www.linkedin.com/uas/oauth2/authorization to authenticate user. I found out the following issue, that I'll explain in detail below.
Positive scenario, everything works as expected:
when using valid client_id, everything is fine. To make everything clear, please see this URL (API key replaced with fake one):
https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=VALID_API_KEY&state=b4ac5e2ab5404d6fad2f25521d83e825&redirect_uri=http%3A%2F%2Flocalhost%3A8085%2Fapply-app%2Fpages%2Fsocial-networks%2Flinkedin%2Fauthenticated%3FsiteIdentifier%3DPIUFK026203F3VBLZ6G79V7OU%26token%3Db4ac5e2ab5404d6fad2f25521d83e825
When I remove client_id, everything is also fine and message is displayed (Missing client_id. A valid client_id is required to proceed.)
But when I use invalid client_id in browser I receive Content Encoding Error and http status code 500. URL: https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=invalid_client_id&state=b4ac5e2ab5404d6fad2f25521d83e825&redirect_uri=http%3A%2F%2Flocalhost%3A8085%2Fapply-app%2Fpages%2Fsocial-networks%2Flinkedin%2Fauthenticated%3FsiteIdentifier%3DPIUFK026203F3VBLZ6G79V7OU%26token%3Db4ac5e2ab5404d6fad2f25521d83e825
And the most interesting part goes here: when I fetch same URL using either wget or even java HttpConnection.connect() there result is different: HTTP status code 200 and html response. But when I started to analyze given output, I noticed that is ends up unexpectedly after <ul class="permissions, so it must me error in your code, that requires fixing.
I reported that, because it's quite inconvenient to support such behavior. Could you please inform me if you have any plans to fix this? If you need any further details regarding steps to reproduce this issue, please do not hesitate to contact me.
Best regards,
Piotr
I am trying to connect to Jira using OAuth. I have followed this manual and I have created app link in Jira instance and configured it with proper consumer key and public key. When I try to request a token using code from the example I am getting 401 with following message (same for python and perl instance):
oauth_problem=consumer_key_unknown
I am out of ideas what can be wrong. I will appreciate any tips.
Well, I believe that I have configured Application link in the wrong place. I have been somehow navigated to the link wiki/admin/listapplicationlinks.action. Then I accidentally found plugins/servlet/applinks/listApplicationLinks which looked pretty much the same as first but content was different. I have added link to the second location and everything works well now. Sorry for confusion.
I also had this similar error. So I then used different "consumer key"(tried to make this unique) other than the given one in the example manual. After searching a lot in internet about this error, I got to know that as most people are using that same consumer key(given in example manual), a database error occurred due to which this error was thrown.
I have been using Google API Client (gapi.auth.authorize) to handle oAuth and it has been working for months until last night. It started with an error saying something like "_.Uu is not a function" last night, and this morning the api URL becomes inaccessible completely (returning 404):
https://apis.google.com//scs/apps-static//js/k=oz.gapi.en_US.wLUinxMaFvQ.O/m=/exm=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTNDbsyHH46eCqa0_JZmh883Ddz23Q/cb=gapi.loaded_1
Is anyone seeing the same problem? Not sure if Google is making any changes.
I had the same problem.
You need to update the client library and then it will work fine.
The same issue is being discussed on another question. It appears that Google knows about it and is working on it.
I am using Twitter4j version 3.0.3.
I am trying to pull follower id and using OAuth. I have been using Twitter4j for years and am relatively experienced with the framework.
However something strange is happening: My program will run fine and then intermittently throw the following stack trace:
Exception in thread "main" 401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.
{"request":"\/1.1\/followers\/ids.json?user_id=20801287&cursor=-1&include_entities=1&include_rts=1","error":"Not authorized"}
Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=92c30ec6 or
http://www.google.co.jp/search?q=19400604
TwitterException{exceptionCode=[92c30ec6-19400604], statusCode=401, message=null, code=-1, retryAfter=-1, rateLimitStatus=RateLimitStatusJSONImpl{remaining=6, limit=15, resetTimeInSeconds=1362898120, secondsUntilReset=890}, version=3.0.3}
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java:177)
at twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java:61)
at twitter4j.internal.http.HttpClientWrapper.get(HttpClientWrapper.java:89)
at twitter4j.TwitterImpl.get(TwitterImpl.java:1817)
at twitter4j.TwitterImpl.getFollowersIDs(TwitterImpl.java:400)
It throws the above at the following line:
IDs ids= twitter.getFollowersIDs(id,cursor);
The above line executes just fine and then without warning fails.
Note: I am checking rate limits and the last time I encountered this the rate limit JSON object pulled by the following line was (below):
RateLimitStatus rls=twitter.getRateLimitStatus().get("/followers/ids")
RateLimitStatusJSONImpl{remaining=7, limit=15, resetTimeInSeconds=1362898120, secondsUntilReset=890}
I thought this might have been an intermittent thing with Twitter, but it has been going on for a few days now.
I've tried it from various machines but get exactly the same problem.
The call fails in this manner, once in approximately 20 calls.
I have also read the similar questions on SE:
Twitter4j 401 Authentication -- However, this is a case where OAuth was not working -- in my case it seems to be working fine until of course when it doesn't.
twitter4j: getting credential errors even though i had set them? -- again not much here that is similar to my case.
Problem in Oauth with twitter4j -- suggest registering the app as a web-app, which I've done, I've filling in the callback url (though it does nothing), but still no luck.
The exception seems to be caused by ids of twitter profiles that may be private.
guys. As mentioned in the title,I wonder whether Shindig implement OAuth2.0 or not? I found an url:http://codereview.appspot.com/3138041/.When I startup the tomcat,however,it throws following exception:
org.apache.http.conn.ConnectTimeoutException: Connect to www.google-analytics.com/www.google-analytics.com/2404:6800:8005:0:0:0:0:61 timed out
I am not sure how to fix this problem and does anyone who encountered this problem before can give me some hints? Thank you in advance!
Yes the 2.5 branch of Shindig does support OAuth 2.0. Shindig contains both a client and provider implementation. The exception you are seeing when starting Tomcat probably has to do with the fact one of the features in Shindig points to that URL and for one reason or another it cannot access the URL. For the most part Shindig should still function properly.