[oauth] Re: new to oauth

The latest core .jar is in http://oauth.googlecode.com/svn/code/maven/net/oauth/core/oauth/20090825/ HttpRequestMessage and OAuthServlet are in http://oauth.googlecode.com/svn/code/maven/net/oauth/core/oauth-provider/20090531/ SampleOAuthProvider is in the .war file in

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

Hi everybody, I'm in pain figuring out whether the oauth_verifier can be sent back from the consumer to the provider in the body of a POST request when other parameters are sent in the authorization header. Here is my situation: I provide an API with OAuth, and one of our users complains he

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

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?

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