What to do with twitter oauth token once retrieved?

I'm writing a web app that will use twitter as its primary log on method. I've written code which gets the oauth token back from Twitter. My plan is now to

1. Find the entry in my Users table for the twitter username retrieved using the token, or create the entry if necessary
2. Update the Users.TwitterOAuthToken column with the new OAuth token
3. Create a permanent cookie with a random guid on the site and insert a record into my UserCookie开发者_如何学Pythons table matching Cookie to User
4. when a request comes in I will look for the browser cookie id in the UserCookies table, then use that to figure out the user, and make twitter requests on their behalf
5. Write the oauth token into some pages as a js variable so that javascript can make requests on behalf of the user
6. If the user clears his/her cookies the user will have to log in again to twitter

Is this the correct process? Have I created any massive security holes?

Sounds good.

However, I suggest not using the Twitter User Name as the primary index for the User table. As Twitter user names can be changed. I learned this the hard way.

You should be fine using the Twitter User ID (big int) as the primary index as it doesn't change if the user changes their user name.

As for the token its self, you are a-okay with storing it for future use. In fact, you are encouraged to do so.

Could you not just save the oauth_token as cookies instead of the GUID and do the user based lookup on the oauth_token or is that bad practice?