And by "web browser" Duane and Bojan are referring to Firefox or Internet Explorer. Not anything in .NET.
On Tue, Jun 30, 2009 at 22:58, DWRoelands<duane.roela...@gmail.com> wrote: > > You can absolutely authenticate in a web page, even if your > application is not a web application. Mine works that way. > > Here's how it should go. Bojan, please correct me if I'm wrong. > > 1. Your application calls GetAuthorizationLink() to get the URL of the > authorization page (you've got this already). > 2. Your application opens a web browser to that link. In .NET, you > can do this with Process.Start(The URL that you get from > GetAuthorizationLink). > 3. The user sees the six-digit PIN on the screen. > 4. Your application prompts the user to enter the six-digit PIN that > they see. > 5. Your application calls GetAccessToken(), passing the six-digit PIN > as the input parameter. > 6. The OAuth object has two properties that should now be populated: > Token and TokenSecret. These are the items you will use for all > subsequent OAuth requests to Twitter. > > Your application should now be authorized via OAuth. > > On Jun 30, 8:58 pm, Obrzut <sa...@peyoteuk.com> wrote: >> This is because of OAuth. It uses HTML pages to validate. Perhaps I am >> wrong - but once I use a web browser to validate - I cannot use a TCP >> Client to get the XML because I authenticated via a web browser. When >> I tried to (for example) send the pin back via a HTTP Web Request it >> failed. I am not sure if I am using the OAuth library Interface Class >> I have for VB.NET correctly!? > > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.