Has anyone explored using the API Connector with Twitter’s 3-legged Oauth process? It’s the only Oauth that lets developers post + delete tweets on a user’s account but requires a temporary token before the Oauth-2 process.
Having some trouble getting the API to authenticate. @emmanuel is this possible with the current connector?
I don’t know. Why wouldn’t it be? Are you hitting some limitations?
I’m hitting an issue with generating a HMAC signature. Any Twitter API request needs a OAuth 1.0 signature which involves taking all of the parameters and running them through an HMAC-SHA1 hashing algorithm. Details here: https://dev.twitter.com/oauth/overview/authorizing-requests
Thanks for your help
Right. The API connector doesn’t support this yet.
Do you know why I can’t connect to twitter, in some reason?