Databases
StackOverflow2013
Postsdbo
POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
    primarykey
    data
    text
    <p>[Cross-posted from the OAuth Ruby Google Group. If you couldn't help me there, don't worry bout it]</p> <p>I'm working on integrating a project with <a href="http://groups.google.com/group/api_tripit/web/tripit-api-documentation---v1" rel="nofollow noreferrer">TripIt's OAuth API</a> and am running into a weird issue.</p> <p>I authenticate fine, I store and retrieve the token/secret for a given user with no problem, I can even make GET requests to a number of services using the gem. But when I try using the one service I need POST for, I'm getting a 401 "invalid signature" response.</p> <p>Perhaps I'm not understanding how to pass in data to the AccessToken's post method, so here's a sample of my code:</p> <pre><code>xml = &lt;&lt;-XML &lt;Request&gt; &lt;Trip&gt; &lt;start_date&gt;2008-12-09&lt;/start_date&gt; &lt;end_date&gt;2008-12-27&lt;/end_date&gt; &lt;primary_location&gt;New York, NY&lt;/primary_location&gt; &lt;/Trip&gt; &lt;/Request&gt; XML` response = access_token.post('/v1/create', {:xml =&gt; xml}, {'Content-Type' =&gt; 'application/x-www-form-urlencoded'}) </code></pre> <p>I've tried this with and without escaping the xml string before hand. The guys at TripIt seemed to think that perhaps the xml param wasn't getting included in the signature_base_string, but when I output that (from lib/signature/base.rb) I see:</p> <p>POST&amp;https%3A%2F%2Fapi.tripit.com%2Fv1%2Fcreate&amp;oauth_consumer_key %3D%26oauth_nonce %3Djs73Y9caeuffpmPVc6lqxhlFN3Qpj7OhLcfBTYv8Ww%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1252011612%26oauth_token %3D%26oauth_version%3D1.0%26xml%3D%25253CRequest%25253E %25250A%252520%252520%25253CTrip%25253E%25250A %252520%252520%252520%252520%25253Cstart_date%25253E2008-12-09%25253C %252Fstart_date%25253E%25250A %252520%252520%252520%252520%25253Cend_date%25253E2008-12-27%25253C %252Fend_date%25253E%25250A %252520%252520%252520%252520%25253Cprimary_location%25253ENew %252520York%252C%252520NY%25253C%252Fprimary_location%25253E%25250A %252520%252520%25253C%252FTrip%25253E%25250A%25253C%252FRequest%25253E %25250A</p> <p>This seems to be correct to me.</p> <p>I output signature (from the same file) and the output doesn't match the oauth_signature param of the Auth header in lib/client/ net_http.rb. It's been URL-encoded in the auth header. Is this correct? </p> <p>Anyone know if the gem is broken/if there's a fix somewhere? I'm finding it hard to trace through some of the code.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USthynctank
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe only thing wrong turneed out to be some carriage returns. Copy/paste from the Web was apparently not the way to go for demoing the API! Thanks for the response! Regarding missing bits, I think maybe Markdown stripped some angle brackets from my code. Anyhow, all is working now.
      singulars
      1. POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
      1. USthynctank
    2. COwhy is your xml tripple url encoded?
      singulars
      1. POIssues POSTing XML to OAuth and Signature Invalid with Ruby OAuth Gem
      1. USThomasReggi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload