1. Yes, a consumer may send some parameters in a header and others in the body.
2. Yes, oauth_verifier is signed; that is, it's included in the Signature Base String. It sounds like the Ruby/Rails software needs work. On Oct 21, 1:31 am, Florent <[email protected]> wrote: > 1. Can the consumer send oauth parameters from various places > (I understand oauth parameter as being part of the signature) ? > 2. Is the oauth_verifier parameter, sent to the provider when > requesting an access token, a parameter part of the signature, or > just a request parameter? > > My understanding is that oauth_verifier is a regular oauth parameter, > so it's part of the signature, and that all signature should be > included in a single place. > > He tells me that the library he uses (a .net lib) works well with > Twitter and Google amongst others. But it won't work with the one > I use (Ruby OAuth + Rails OAuth plugin). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
