Hi Andrew, You should store the oauth_token and oauth_token_secret (securely) you received alongside any kind of identifying data you have for your user. Then, when making subsequent API calls, you use the access token to represent the user's permission and identity. You don't need to re-authenticate the user against Twitter every time (unless you want to).
Taylor On Tue, Oct 12, 2010 at 4:08 AM, Andrew Cross. Gna <success....@gmail.com>wrote: > I have used the function to authenticate my application with the user > and allow it to access the twitter functionalist from my web site. The > function does everything correctly and gets the oauth_ details. > > If I want to skip the authentication required from the user until he > rejects my application from his application list from the Twitter. I > require to use his first time authenticated details instead of asking > the credentials again and again. I store every credentials in a local > variable and formed the URLs with the required details. But, it throws > "The remote server returned an error: (401) Unauthorized." > > How to avoid the approval from the registered user in twitter on every > time my application request to connect with the Twitter and fetch the > details. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
