On Feb 17, 10:47 pm, Ryan Alford ryanalford...@gmail.com wrote:
You order all parameters EXCEPT the signature, then create the signature,
then append the signature to the end. All other parameters should be in
order.
I am under the impression that sorting is only required to generate
the
You order all parameters EXCEPT the signature, then create the signature,
then append the signature to the end. All other parameters should be in
order.
I am under the impression that sorting is only required to generate
the Signature Base String. I haven't seen anything in the OAuth spec
Even with the URL like this:
http://twitter.com/oauth/request_token?oauth_consumer_key=valueoauth_nonce=1266501098oauth_signature_method=HMAC-SHA1oauth_timestamp=1266500348oauth_version=1.0oauth_signature=eGALeAVpxt4CB%2FuHfkLq51%2FWXRk%3D
It still fails for me. I've gotta be missing something
Can you post the string that you hash to create the signature?
Ryan
On Thu, Feb 18, 2010 at 8:42 AM, Berto mstbe...@gmail.com wrote:
Even with the URL like this:
http://twitter.com/oauth/request_token?oauth_consumer_key=
GEThttp%3A%2F%2Ftwitter.com%2Foauth%2Frequest_tokenoauth_consumer_key
%3D8hvUTsGttoOBN2ygbDVJw%26oauth_nonce
%3D1266502068%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1266501208%26oauth_version%3D1.0
On Feb 18, 8:04 am, Ryan Alford ryanalford...@gmail.com wrote:
Can you post the
That looks fine.
Are you using the Consumer Secret as the key to the hash?
Ryan
On Thu, Feb 18, 2010 at 9:10 AM, Berto mstbe...@gmail.com wrote:
GEThttp%3A%2F%2Ftwitter.com%2Foauth%2Frequest_tokenoauth_consumer_key
%3D8hvUTsGttoOBN2ygbDVJw%26oauth_nonce
Fixed by putting an after my consumer secret. So essentially, it
was just that my parameters were out-of-order.
Thanks, Ryan!
On Feb 18, 9:01 am, Ryan Alford ryanalford...@gmail.com wrote:
That looks fine.
Are you using the Consumer Secret as the key to the hash?
Ryan
On Thu, Feb 18,
Correct. I'm using the exact values provided from my application
registration. And I've verified the algorithm works with the example
from the oauth spec.
On Feb 18, 9:01 am, Ryan Alford ryanalford...@gmail.com wrote:
That looks fine.
Are you using the Consumer Secret as the key to the hash?
To answer the first email, I was doing that so I could put it in the
request header's authorization field to get this effect:
(Taken from oauth.net)
Authorization: OAuth realm=http://sp.example.com/;,
oauth_consumer_key=0685bd9184jfhq22,
Your querystring parameters are in the wrong order. You have the
oauth_nonce AFTER oauth_timestamp. It needs to be before it. The
parameters must be in order.
Ryan
Sent from my DROID
On Feb 17, 2010 6:18 PM, Berto mstbe...@gmail.com wrote:
To answer the first email, I was doing that so I
Nevermind, just re-read the normalizing parameters part of the spec.
I'll try it out tomorrow.
Thanks.
On Feb 17, 5:27 pm, Ryan Alford ryanalford...@gmail.com wrote:
Your querystring parameters are in the wrong order. You have the
oauth_nonce AFTER oauth_timestamp. It needs to be before it.
I thought that was only for the signature which is in the right
order?
Ryan Alford wrote:
Your querystring parameters are in the wrong order. You have the
oauth_nonce AFTER oauth_timestamp. It needs to be before it. The
parameters must be in order.
Ryan
Sent from my DROID
On Feb 17,
You order all parameters EXCEPT the signature, then create the signature,
then append the signature to the end. All other parameters should be in
order.
Ryan
On Wed, Feb 17, 2010 at 6:42 PM, Berto mstbe...@gmail.com wrote:
I thought that was only for the signature which is in the right
13 matches
Mail list logo
