[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

No, that's for both the generation of the signature and the request.  I just
tested it.  If the parameters are not in the correct order, the request will
fail with a "401 Unauthorized" error.  In my test, I put the timestamp
before the nonce.  The request failed.  If I put the parameters in order,
the request is successful.

On Wed, Oct 7, 2009 at 8:14 AM, JDG  wrote:

> That's simply for generating the signature base string. it does not matter
> when you're actually sending the parameters.
>
>
> On Wed, Oct 7, 2009 at 05:33, ryan alford  wrote:
>
>> Here is the documentation on ordering the parameters...
>> http://oauth.net/core/1.0#anchor14
>>
>> Section 9.1.1
>>
>> Parameters are sorted by name, using lexicographical byte value ordering.
>> If two or more parameters share the same name, they are sorted by their
>> value.
>>
>> This is excluding the oauth_signature parameter.
>>
>> Ryan
>>  
>>
>> On Wed, Oct 7, 2009 at 6:11 AM, ryan alford wrote:
>>
>>> Yes, the order does matter. All parameters need to be in order except
>>> for the signature. The signature should be last and should have been
>>> generated with all of the parameters in the correct order.
>>>
>>>
>>>
>>> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>>>
>>> >
>>> > The order of parameters shouldn't matter.  What library are you using
>>> > to generate the url?
>>> >
>>> > On Oct 6, 8:51 pm, ryan alford  wrote:
>>> >> The signature needs to be at the end of the URL, not sorted with the
>>> >> other parameters.
>>> >>
>>> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>>> >>
>>> >>
>>> >>
>>> >>> I am trying to run a sample app
>>> >>> but i am getting 401 error during request_token phase.
>>> >>
>>> >>> Failed to validate oauth signature and token
>>> >>
>>> >>> this is what i am accessing:
>>> >>
>>> >>>
>>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>>> >>> ...
>>> >>
>>> >>> What's problem this sentence
>>> >>> Anybody help me plz..
>>>
>>
>>
>
>
> --
> Internets. Serious business.
>

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[JDG]

That's simply for generating the signature base string. it does not matter
when you're actually sending the parameters.

On Wed, Oct 7, 2009 at 05:33, ryan alford  wrote:

> Here is the documentation on ordering the parameters...
> http://oauth.net/core/1.0#anchor14
>
> Section 9.1.1
>
> Parameters are sorted by name, using lexicographical byte value ordering.
> If two or more parameters share the same name, they are sorted by their
> value.
>
> This is excluding the oauth_signature parameter.
>
> Ryan
>  
>
> On Wed, Oct 7, 2009 at 6:11 AM, ryan alford wrote:
>
>> Yes, the order does matter. All parameters need to be in order except
>> for the signature. The signature should be last and should have been
>> generated with all of the parameters in the correct order.
>>
>>
>>
>> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>>
>> >
>> > The order of parameters shouldn't matter.  What library are you using
>> > to generate the url?
>> >
>> > On Oct 6, 8:51 pm, ryan alford  wrote:
>> >> The signature needs to be at the end of the URL, not sorted with the
>> >> other parameters.
>> >>
>> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>> >>
>> >>
>> >>
>> >>> I am trying to run a sample app
>> >>> but i am getting 401 error during request_token phase.
>> >>
>> >>> Failed to validate oauth signature and token
>> >>
>> >>> this is what i am accessing:
>> >>
>> >>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>> >>> ...
>> >>
>> >>> What's problem this sentence
>> >>> Anybody help me plz..
>>
>
>


-- 
Internets. Serious business.

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

Here is the documentation on ordering the parameters...
http://oauth.net/core/1.0#anchor14

Section 9.1.1

Parameters are sorted by name, using lexicographical byte value ordering. If
two or more parameters share the same name, they are sorted by their value.

This is excluding the oauth_signature parameter.

Ryan


On Wed, Oct 7, 2009 at 6:11 AM, ryan alford  wrote:

> Yes, the order does matter. All parameters need to be in order except
> for the signature. The signature should be last and should have been
> generated with all of the parameters in the correct order.
>
>
>
> On Oct 7, 2009, at 12:10 AM, jmathai  wrote:
>
> >
> > The order of parameters shouldn't matter.  What library are you using
> > to generate the url?
> >
> > On Oct 6, 8:51 pm, ryan alford  wrote:
> >> The signature needs to be at the end of the URL, not sorted with the
> >> other parameters.
> >>
> >> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
> >>
> >>
> >>
> >>> I am trying to run a sample app
> >>> but i am getting 401 error during request_token phase.
> >>
> >>> Failed to validate oauth signature and token
> >>
> >>> this is what i am accessing:
> >>
> >>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
> >>> ...
> >>
> >>> What's problem this sentence
> >>> Anybody help me plz..
>

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

Yes, the order does matter. All parameters need to be in order except
for the signature. The signature should be last and should have been
generated with all of the parameters in the correct order.



On Oct 7, 2009, at 12:10 AM, jmathai  wrote:

>
> The order of parameters shouldn't matter.  What library are you using
> to generate the url?
>
> On Oct 6, 8:51 pm, ryan alford  wrote:
>> The signature needs to be at the end of the URL, not sorted with the
>> other parameters.
>>
>> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>>
>>
>>
>>> I am trying to run a sample app
>>> but i am getting 401 error during request_token phase.
>>
>>> Failed to validate oauth signature and token
>>
>>> this is what i am accessing:
>>
>>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS
>>> ...
>>
>>> What's problem this sentence
>>> Anybody help me plz..

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[uooooookeng]

Sorry
I don't understand
means : oauth_signature must be position URL's end
ex )
http://twitter.com/oauth/request_token?oauth_version=1.0&oauth_nonce=3797601334037614568&oauth_timestamp=1254888471&oauth_consumer_key=xkz0POdiAXiC2S8hE0TfXA&oauth_signature_method=HMAC_SHA1&oauth_signature=aXhp2YoBnzCp12198YmrRq4VfJWA2dDYEeXxh2so1Gs
On 10월7일, 오후12시51분, ryan alford  wrote:
> The signature needs to be at the end of the URL, not sorted with the
> other parameters.
>
> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>
>
>
>
>
> > I am trying to run a sample app
> > but i am getting 401 error during request_token phase.
>
> > Failed to validate oauth signature and token
>
> > this is what i am accessing:
>
> >http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS...
>
> > What's problem this sentence
> > Anybody help me plz..- 원본 텍스트 숨기기 -
>
> - 원본 텍스트 보기 -

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[jmathai]

The order of parameters shouldn't matter.  What library are you using
to generate the url?

On Oct 6, 8:51 pm, ryan alford  wrote:
> The signature needs to be at the end of the URL, not sorted with the
> other parameters.
>
> On Oct 6, 2009, at 11:47 PM, uookeng  wrote:
>
>
>
> > I am trying to run a sample app
> > but i am getting 401 error during request_token phase.
>
> > Failed to validate oauth signature and token
>
> > this is what i am accessing:
>
> >http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS...
>
> > What's problem this sentence
> > Anybody help me plz..

[twitter-dev] Re: [twitter Dev] Failed to validate oauth signature and token

[ryan alford]

The signature needs to be at the end of the URL, not sorted with the
other parameters.



On Oct 6, 2009, at 11:47 PM, uookeng  wrote:

>
> I am trying to run a sample app
> but i am getting 401 error during request_token phase.
>
> Failed to validate oauth signature and token
>
> this is what i am accessing:
>
> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHSj96enwxUEw&oauth_signature_method=HMAC_SHA1&oauth_signature=25wyvtXGlrGZmOElOVpLnhtJNIOi1yIbx6Qa4E7V6h0&oauth_timestamp=1254884036&oauth_nonce=3797601334037614568&oauth_version=1.0
>
> What's problem this sentence
> Anybody help me plz..