Yes, the access token need to save in database. And I also have the same question. If user came again so we use cookies to get his username and will lookup in database for access token and land it home page.

So I think cookie need to be involved.

When you say “Also, you should persist the access token so that you can use it again in the future.”

You mean like store it in database. I have usecase like twitterfeed. twitterfeed takes twitter username and password only once. But after it works by itself. You mean here twitterfeed is sotring some info in database.

I haven’t tried the technique you’re saying and I think it’s hard.

What I did was to get the token and token secret from the access token and associate it with a user. Then, I save it to the database.

When I need the access token again because, say, the user needs to access his Twitter account via my app, I just get the token and tokensecret associated with the user and reconstruct the access token again.

If I am not mistaken you can do it by

AccessToken accessToken = new AccessToken(token, tokenSecret);

That will give you the access token that you got initially.

I don’t know though if this will work. It’s been a while since I used Twitter4J and judging from the emails in the discussion groups so much has changed since then.

Try verifying via the documentation.

Goodluck!

You this post was very helpful to me to understand all this concept.
http://jeungun.wordpress.com/2009/09/03/quick-and-dirty-twitter4j-oauth-for-web-apps/

So to save these access tokens, I have to use cookies. I will get username from cookie, will fetch access tokens from database and user will in.

This is what I am thinking if I save access tokens in DB. What you think about this technique, or you have any other idea.

Thanks for blogging on OAuth.