It sounds like the ruby library may be accidentally pulling in those parameters. I think Perryn posted to the oauth-ruby list, where we should continue this discussion.
b. On Mon, Feb 2, 2009 at 4:07 PM, Eran Hammer-Lahav <[email protected]> wrote: > > OAuth core does not support body signatures expect for www-encoded-form. > > EHL > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf >> Of Perryn Fowler >> Sent: Monday, February 02, 2009 4:37 AM >> To: OAuth Ruby >> Cc: [email protected] >> Subject: [oauth] signing post requests >> >> >> I have set up a small test consumer app and a small test provider app >> - both rails apps. >> The consumer app is using the oauth ruby gem and the provider app is >> using the plugin. >> (I have found and addressed the issues that have been mentioned here >> recently with the plugin and the new version of the gem) >> >> I am trying to post some XML from the consumer app to the provider app >> and authorize it via oAuth. >> >> Unfortunately I keep getting signature verification errors. >> >> The problem seems to be that the raw XML is being posted as the >> request body. The consumer app does not appear to consider this to >> qualify as a 'parameter' for the purposes , while the provider app >> does ( probably because rails does?) >> >> Admittedly the spec only really mentions bonafide parameters, but it >> would seem in this use case you would definately want to have the xml >> payload included in the signature.. >> >> or have I missed something? >> >> >> cheers >> Perryn >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
