#1

I created a new app today & wanted to generate an access_token/access_token_secret for our twitter account via the dashboard. I generated the secrets, but they were created with only read permissions. The dashboard & docs provided no obvious way to convert these secrets to ones with write permissions.

Only after a lot of frustration and trying random stuff did I realize that I could get a token with write permissions by:

  • enabling oauth 1.0a on the app (with bogus auth urls, since we have no plans for an auth flow for this app)
  • updating oauth 1.0a permissions to read/write
  • save user auth settings
  • regenerating the access_token
  • turning off oauth 1.0a

This flow is not described in docs anywhere (that I could find) and is unnecessarily clunky.

It would be great if while generating tokens from the App “Keys and Tokens” page we could select permissions with which to generate the tokens.

1 Like
#2

I think it was impossible since the token generated is generated Once by a set of consumer keys and permission access. One user - one set of consumer keys - one permission access.