-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth2 for twitter don't work #143
Comments
Well, if you look at the first param, there is an error:
I'm trying to do the same, but it seems that OAuth2 puts the params such has |
And you're sure this is nothing to do with: https://dev.twitter.com/blog/api-v1-is-retired ? |
Oh yes, it has, definitely. Personally I was still on wild query to get my timeline, no auth at all. So now I have to implement that and I thought my use case needs this app-only auth. This issue was recent and I thought I'd expose my findings. |
@qur2 I'm not too sure, but it certainly looks as though its an issue with your specific configuration rather than the actual library itself :) |
I'm not even sure it's the library to use for those twitter application-only requests. I'm trying to achieve the same as the bug reporter and saw that there was an error. So his problem is not the Right now I'm digging on passportjs side as I already rely on it. If it's just for me, you can close the bug, I won't miss it 🔨 |
Yeah, this doesn't work. I was trying to use Oauth2.get() in the way shown on this site: http://webapplog.com/node-js-oauth1-0-and-oauth2-0-twitter-api-v1-1-examples/ The solution was just to make a normal HTTP request, like so: https://gist.github.com/Dakuan/5899971 Otherwise I was getting this: { statusCode: 400, data: '{"errors":[{"message":"Bad Authentication data","code":215}]}' } |
You could also override the prototype of |
access_token
return undefinedThe text was updated successfully, but these errors were encountered: