JDG, Thanks for the reply. I didn't realize that I needed to include an oauth_callback parameter for getting the ACCESS TOKEN. I knew I could supply one (optional) when getting the REQUEST TOKEN. I thought it would automatically callback to the application I created with Twitter. I'm also not sure what you mean by the oob flow?
-Matt On Jul 31, 3:20 pm, JDG <ghil...@gmail.com> wrote: > Since you're not including an oauth_callback, i would assume you're using > the oob flow, in which case, i have to ask, where's your oauth_verifier > parameter? > > On Fri, Jul 31, 2009 at 13:09, mattarnold1977 > <matt.arnold.1...@gmail.com>wrote: > > > > > > > > > Please, if anyone can assist I would be grateful. Here is a sample of > > my url I've formed to get the access token: > > >http://twitter.com/oauth/access_token?oauth_consumer_key=myconsumerke... > > > -Matt > > > On Jul 30, 7:49 pm, mattarnold1977 <matt.arnold.1...@gmail.com> wrote: > > > I am using ASP .NET (VB) to try and authenticate using oAuth. I have > > > been able to get a request token and direct a user to Twitter's > > > authentication page. Twitter then redirects back to my app. At that > > > point I attempt to get an access token, but I continue to receive 401 > > > "unauthorized" errors. I have made sure that I am getting a new > > > signature, using both the token and token secret when generating the > > > signature, and that my url parameters are in alphabetical order, but I > > > continue to get 401 errors. Has anyone experienced this, and if so, > > > could you point me in the right direction toward diagnosing this > > > issue? > > > > -Matt > > -- > Internets. Serious business.
