Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Invalid Signature
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  9 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Liyan Zhao  
View profile  
 More options Feb 24 2012, 10:30 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Fri, 24 Feb 2012 07:30:24 -0800 (PST)
Local: Fri, Feb 24 2012 10:30 am
Subject: Invalid Signature
Hi,

I'm trying to integrate TripIt with my website, and have hit a
blocker.

To get an access token, I've generated a request like below:
https://api.tripit.com/oauth/request_token?oauth_signature_method=HMA...

However TripIt responded with :
<Response>
<Error>
<code>401</code>
<detailed_error_code>104.1</detailed_error_code>
<description>invalid signature</description>
</Error>
</Response>

I've independently verified that the signature I'm sending is correct
by using this tool:
http://developer.netflix.com/resources/OAuthTest

Any idea why TripIt thinks it's invalid?

Cheers,
Liyan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liyan Zhao  
View profile  
 More options Feb 27 2012, 5:28 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Mon, 27 Feb 2012 02:28:31 -0800 (PST)
Local: Mon, Feb 27 2012 5:28 am
Subject: Re: Invalid Signature
Hi,

I'm really stuck, could anyone shed light on this?

Cheers,
Liyan

On Feb 24, 3:30 pm, Liyan Zhao <liyan.z...@openjawtech.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Thor Denmark  
View profile  
 More options Feb 27 2012, 1:08 pm
From: Thor Denmark <tdenm...@gmail.com>
Date: Mon, 27 Feb 2012 10:08:53 -0800
Local: Mon, Feb 27 2012 1:08 pm
Subject: Re: Invalid Signature

Hi Liyan --

Are you using one of our API client libraries (available
here<http://tripit.github.com/api/>)
to connect to api.tripit.com?  If so, those should work out of the box with
no hassle and I recommend using them for ease of integration.  If not, what
library(s)/OS/platform are you using?  We can try to help you debug client
code to a certain extent, but no promises.  With an invalid signature
error, the first thing I'd need from you for a particular failure would be
the consumer key involved in the failure, the approximate date/time (and
your timezone) of the failure, and the exact oauth signature base string
value generated by your client oauth request generation code.

    /thor

On Mon, Feb 27, 2012 at 2:28 AM, Liyan Zhao <liyan.z...@openjawtech.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liyan Zhao  
View profile  
 More options Feb 28 2012, 6:51 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Tue, 28 Feb 2012 03:51:39 -0800 (PST)
Local: Tues, Feb 28 2012 6:51 am
Subject: Re: Invalid Signature
Thanks Thor for replying.

I was using a third party JS library for OAuth. Since I was blocked by
the aforementioned issue, I just switched over to using your Java API.

The Java lib got me further. However I'm facing another issue.

My goal is to publish user's itinerary into their TripIt account. I've
got the OAuth stuff working, but have problems with the create api.

I always get HTTP400 when I post my travel object to the url.

Not sure how to attach files here, so here's my request in xml. It
validates against the xsd posted on your api site. My client key is:
c9e88e98c45b948b1bb0371599f522ab60b2005b
<Request>
    <AirObject>
        <is_client_traveler>true</is_client_traveler>
        <booking_site_name>Right Destinations</booking_site_name>
        <booking_site_phone>1-800-123-456-1</booking_site_phone>
        <booking_site_url>http://www.rightdestinations.com</
booking_site_url>
        <supplier_conf_num>5LRQ7N</supplier_conf_num>
        <Segment>
            <StartDateTime>
                <date>2012-03-17</date>
                <time>16:00:00</time>
            </StartDateTime>
            <EndDateTime>
                <date>2012-03-17</date>
                <time>19:35:00</time>
            </EndDateTime>
            <start_city_name>Dublin</start_city_name>
            <end_city_name>Barcelona</end_city_name>
            <marketing_airline>EI</marketing_airline>
            <marketing_flight_number>50120</marketing_flight_number>
        </Segment>
        <Segment>
            <StartDateTime>
                <date>2012-03-31</date>
                <time>16:55:00</time>
            </StartDateTime>
            <EndDateTime>
                <date>2012-03-31</date>
                <time>19:25:00</time>
            </EndDateTime>
            <start_city_name>Barcelona</start_city_name>
            <end_city_name>Dublin</end_city_name>
            <marketing_airline>IB</marketing_airline>
            <marketing_flight_number>50130</marketing_flight_number>
        </Segment>
        <Traveler>
            <first_name>Liyan</first_name>
            <last_name>Zhao</last_name>
        </Traveler>
    </AirObject>
</Request>

On Feb 27, 6:08 pm, Thor Denmark <tdenm...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liyan Zhao  
View profile  
 More options Feb 28 2012, 6:58 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Tue, 28 Feb 2012 03:58:59 -0800 (PST)
Local: Tues, Feb 28 2012 6:58 am
Subject: Re: Invalid Signature
Here's the auth header:

OAuth oauth_token="894af69220a17b1ca31058fc03ee55de809ad3e0",
oauth_consumer_key="c9e88e98c45b948b1bb0371599f522ab60b2005b",
oauth_signature_method="HMAC-SHA1", oauth_
timestamp="1330430191", oauth_nonce="525754364720236",
oauth_version="1.0", oauth_signature="DAXjucKVlL9NiD5FktpHEyDg7kk%3D",
oauth_token="894af69220a17b1ca31058fc03ee55de809ad3e0"

Cheer,
Liyan

On Feb 28, 11:51 am, Liyan Zhao <liyan.z...@openjawtech.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Thor Denmark  
View profile  
 More options Feb 28 2012, 1:41 pm
From: Thor Denmark <tdenm...@gmail.com>
Date: Tue, 28 Feb 2012 10:41:50 -0800
Local: Tues, Feb 28 2012 1:41 pm
Subject: Re: Invalid Signature

Hi Liyan --

HTTP 400 indicates a bad request.  Did you inspect the response content to
the failed request below?  In that respones content you should see a
specific error message indicating what was wrong with the request.  If you
don't see that, then please also send along the exact date/time (and
timezone you're in) for either the failed request below, or invoke another
failed request and send along the time of that incident.
Thanks.

    /thor

On Tue, Feb 28, 2012 at 3:51 AM, Liyan Zhao <liyan.z...@openjawtech.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liyan Zhao  
View profile  
 More options Feb 29 2012, 6:10 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Wed, 29 Feb 2012 03:10:37 -0800 (PST)
Local: Wed, Feb 29 2012 6:10 am
Subject: Re: Invalid Signature
Hi Thor,

I've just send another create request.

Here's the debug info on my side. The server date returned was: Wed,
29 Feb 2012 11:08:09 GMT. It has the auth header, and request xml. I'm
trying to create a trip on behave of TripIt user: liyan.zhao at
openjawtech.com

>>>>>>>> HTTP request:

POST /v1/create
Content-Type: text/xml; charset=UTF-8
Authorization: OAuth realm="https%3A%2F%2Fapi.tripit.com%2F",
oauth_token="894af69220a17b1ca31058fc03ee55de809ad3e0",
oauth_consumer_key="c9e88e98c45b948b1bb0371599f522ab60b2005b",
 oauth_signature_method="HMAC-SHA1", oauth_timestamp="1330513601",
oauth_nonce="609399548374793", oauth_version="1.0",
oauth_signature="QeZbkuf0adm%2B4qDUQm116eU4e9E%3D"

<Request><AirObject><is_client_traveler>true</
is_client_traveler><booking_site_name>Right Destinations</
booking_site_name><booking_site_phone>1-800-123-456-1</
booking_site_phone><b
ooking_site_url>http://www.rightdestinations.com</
booking_site_url><supplier_conf_num>5LRQ7N</
supplier_conf_num><Segment><StartDateTime><date>2012-03-17</
date><time>16:00:00</time>
</StartDateTime><EndDateTime><date>2012-03-17</date><time>19:35:00</
time></EndDateTime><start_city_name>Dublin</
start_city_name><end_city_name>Barcelona</end_city_name><marketing_a
irline>EI</marketing_airline><marketing_flight_number>50120</
marketing_flight_number></Segment><Traveler><first_name>Liyan</
first_name><last_name>Zhao</last_name></Traveler></AirOb
ject></Request>
<<<<<<<< HTTP response:
HTTP/1.1 400 Bad Request
Server: nginx
Date: Wed, 29 Feb 2012 11:08:09 GMT
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive

        at
net.oauth.client.OAuthResponseMessage.toOAuthProblemException(OAuthResponse Message.java:
83)

On Feb 28, 6:41 pm, Thor Denmark <tdenm...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liyan Zhao  
View profile  
 More options Feb 29 2012, 6:13 am
From: Liyan Zhao <liyan.z...@openjawtech.com>
Date: Wed, 29 Feb 2012 03:13:18 -0800 (PST)
Local: Wed, Feb 29 2012 6:13 am
Subject: Re: Invalid Signature
Missed the top part of the debug info:

net.oauth.OAuthProblemException: HTTP/1.1 400 Bad Request
URL: https://api.tripit.com/v1/create
oauth_signature base string: POST&https%3A%2F%2Fapi.tripit.com
%2Fv1%2Fcreate&oauth_consumer_key
%3Dc9e88e98c45b948b1bb0371599f522ab60b2005b%26oauth_nonce
%3D609399548374793%26oauth_s
ignature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1330513601%26oauth_token
%3D894af69220a17b1ca31058fc03ee55de809ad3e0%26oauth_version%3D1.0

>>>>>>>> HTTP request:

...same as the section posted previously...

On Feb 29, 11:10 am, Liyan Zhao <liyan.z...@openjawtech.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Thor Denmark  
View profile  
 More options Mar 1 2012, 7:34 pm
From: Thor Denmark <tdenm...@gmail.com>
Date: Thu, 1 Mar 2012 16:34:50 -0800
Local: Thurs, Mar 1 2012 7:34 pm
Subject: Re: Invalid Signature

Hi Liyan --

If you look at the response body content for that request I believe you'll
see the following error message string being rendered back to your client:
"no document present under request parameter key 'xml'".  TripIt almost
always renders errors back to you in the response content.

What this particular error means is that you're not putting an http POST
request parameter key in front of your urlencoded xml document which is
also apparent from the info you include below (thanks for all the details!).

So, instead of a POST payload starting with "<Request><AirOb....", try
signing the request with POST request content that starts with "*xml=*
<Request><AirOb....".

Cheers.

    /thor

On Wed, Feb 29, 2012 at 3:10 AM, Liyan Zhao <liyan.z...@openjawtech.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »