[twitter-dev] Long String Signing

2009-11-29 Thread abruton
Hi All I'm battling with the oauth stuff, but it looks like my HMAC-SHA1 hashing does not generate the right strings for long input strings. Eg: I enter the following: Normalised Parameters: oauth_consumer_key=keyoauth_nonce=1112009295818146IJ2592BY08TKD28W8IHG5179oauth_signature_method=HMAC-

Re: [twitter-dev] Long String Signing

2009-11-29 Thread Mark McBride
The online one is giving you a base 64 encoded value (which should be used). The string you gave (8B0E9AFC15E265C49A687F7FC0C389A1F0B791C3) looks like it's a hex representation of a byte array. Can you try to base 64 encode that and see if there are differences? ---Mark On Sun, Nov 29, 2009