Well, seems that if I want to sign in with Twitter https://dev.twitter.com/docs/auth/implementing-sign-twitter I need to provide “signature”. So I can get access_token and access_token_secret.
But creating signature https://dev.twitter.com/docs/auth/creating-signature means I need to provide access_token_secret (using it on the signing key), which I can’t have it if I previously request it.
So what’s up? I always get
The remote server returned an error: (401) Unauthorized., even using the access_token_secret generate by the Application Interface.
Should I create signature key in some other way?