Yes, this is also a way, an easier way.... This is because generally the authorized and unauthorized request tokens are literally the same. Once the user grants access, the token is said to be authorized. But in case, when the authorized and unauthorized request tokens are literally different (I don't know if this is allowed by the protocol), this method will not work. In that case, the user will have to take some pain.
-Dipen kellan wrote: > In the desktop flow you generally have the consumer display a big pink > button reading, "Thanks, I've authorized you, lets continue" or some > such, that the user clicks when they've finished the authorization > step with the SP. At which point the Consumer makes its request to > the Access Token URL. Other tricks are possible, but they require a > fair amount of coordination between the Consumer and the SP. > > -kellan > > On Thu, Jan 1, 2009 at 10:12 AM, Nouman Ashraf <[email protected]> wrote: > >> Hi All, >> I am going to implement OAuth protocol in my desktop application >> (consumer) with a web service(service provider) but i am confused that >> how service provider redirect user back to consumer with authenticated >> request token. i.e. how can i get that authenticated request token and >> come to know in a desktop application that the user get validated etc. >> etc... >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
