-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 DWRoelands 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. Hi Duane,
This is absolutely the correct workflow. Regards, Bojan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKSuREAAoJEO4IwQyHg9AWos4QAMXmZ+jbyoBHVDtisui99qna NDo/VRq/QVrf+QUaspWQacilc8vjhT+mQpehdkhaaHO2fy7vuu+K07mttkdLDpPQ pEater5dGNR52sOacbhU4S6VUoWHktGQyW0OIrYIP2jGWlO7Jh0dGqN4zgOz/CWX RlFn8Ys7RGGazo6fTPQjfrWX0+ut4OrMUkgF2XaM/GqpI8coKXopIGUYbqVjRl8Y MtdGxIBefPrxAr4VTTHcJDeHbgsj6fdnBYaPyeCEB6IA+V3Dg4yV5ur0I4x53Bdy FoFqtVZG37tXm88Wl3zzWskfQ1EmA9IhcY5jd0tC9/k0MxDvq1gJ47pFlpf/QXHF vZwCGVRZXic6KDk5W6cTPMWSE9GdkIuDYJRpp3XCTLeovV5kdBoKRA0Dc1tYROvR x7NsNHInk/ELMXHoeEQajZW2Sech/6Ak3WH4Hh1Sj0hAgARfLqcIQEzyl16Mln+z iAq3BGjFeJGA5CYkIvYkCTL30tpv60mZXG/deNBZ1Sp1zFg10y39JGECWV4xZT0l dtBaMHLf1t6JfBFWS0AHenUZqVa62+o2Cl1km5pRClWtXwbkVZ0MfCGgdkgWFj7h EeLId4HeoNdwjJt9PLaKFfymzCPaMkiNBrL4SFLJSgm9lkqXMv7LEdKX6i0P5F1+ gUhdvPht/+N08PK2ZYYG =iw7j -----END PGP SIGNATURE-----
