[oauth] Re: (request access token) Should oauth_verifier be in the same place than other oauth_ parameters?

2009-10-22 Thread Pelle Braendgaard
What version of the Ruby gem and Rails plugin are you using? The current versions do support the full 1.0a flow. If you have an older version there could be problems. Please see the following article about updating to newer versions.

[oauth] Re: (request access token) Should oauth_verifier be in the same place than other oauth_ parameters?

2009-10-21 Thread John Kristian
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 florentvauce...@gmail.com wrote: 1. Can the

[oauth] Re: (request access token) Should oauth_verifier be in the same place than other oauth_ parameters?

2009-10-21 Thread Paul Osman
Hi Florent, I certainly couldn't see anything in the spec that addresses sending OAuth parameters using a combination of GET, POST or Authorization headers. While I certainly think that it's a strange thing to do (seems like more work for the Consumer Developer), I think as a Service