Struggling to get twitter auth setup #1280
Replies: 2 comments 1 reply
-
I'm not sure about "Elevated access" as at the time we have added twitter support oauth1 was the only way with twitter and this is what go-pkgz/auth implements. See this pr for details. Btw, none of my twitter "apps" require elevated access, but maybe this is a thing for new apps, not sure. The best way to proceed here is to open a ticket in go-pkgz/auth and mention the author of that PR, so he could check it and hopefully address the issue. If Twitter is really supporting oauth2 these days, adding it to auth providers should be a relatively easy task. |
Beta Was this translation helpful? Give feedback.
-
Did a bit more research last night/this morning and found this regarding the Elevated/Essential Access confusion (seen here https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api):
So for those who setup their accounts before that date, their apps will work fine - anyone coming to this project after that and wanting to use twitter auth with be required to use oauth 2 unless the apply for elevated access (which puts you on a waitlist) - I'll go ahead and move over to go-pkgz/auth and continue the conversation there, just wanted to leave this here in case anyone stops by and is confused on all the run-around. |
Beta Was this translation helpful? Give feedback.
-
As the title says, I'm struggling to get my twitter auth setup for commenting on my blog. I've followed the instructions on the docs as close as possible but I think things have changed since it was written and I don't know what I'm missing. I have my consumer api key and consumer secret key - but when I log in with my twitter account I get this in the debug logs:
I hyper-focused in on this line:
got raw user info map[errors:[map[code:453 message:You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve]]]
but applying for Elevated access seems unnecessary, so am I missing something? I've tried both 1.0 oauth and 2.0 oauth to no success either way. I'd also be more than happy to update the docs if it would help make things easier to understand for those coming after me.Beta Was this translation helpful? Give feedback.
All reactions