Reusing OAuth token and secret when Consumer key is changed in Twitter application (Rails)

Question

I am working in a Rails application in which i use OmniAuth to authenticate user with Twitter. Once user is authenticated properly, i then get the OAuth Token and OAuth Secret from Twitter.

I can then use this token and secret pairs to make api calls from my Rails application.

Consumer key from my twitter application is used to make api calls along with users token and secret.

Now, when my consumer key (of my twitter app) is changed. All the previously obtained OAuth token and secret are not working (i cannot use it to make api call).

How should i handle this situation when the consumer key is changed?

is there any way to refresh the Oauth token and secret with new consumer key without prompting user again to authenticate with twitter?

score 2 · Accepted Answer · answered Aug 02 '12 at 05:06

2

If you changed the consumer keys it means you are using different twitter application, how old application token supports new application? its not possible to merge two twitter application tokens.

Once you changed the consumer key, user again needs to authenticate the new twitter application.

answered Aug 02 '12 at 05:06

Krishna Srihari

714
6
6

So i should not change Twitter application once i have set it to use authenticate users? i mean the consumer key. – balanv Aug 02 '12 at 05:54
yes, you should not change consumer key, once its changed this is new twiiter application. – Krishna Srihari Aug 03 '12 at 06:21

Reusing OAuth token and secret when Consumer key is changed in Twitter application (Rails)

1 Answers1