What algorithm you're using for hmac-sha1 and base64

I'm getting different oauth_signature for the xAuth test example
http://dev.twitter.com/pages/xauth

Nikolay Klimchuk

On Sep 13, 1:01 am, Double K <squel...@gmail.com> wrote:
> hi, my name is Kim.
> I will make XAuth module. So i need developer help.
> i make signature base string
> for example
>
> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> %26x_auth_password%3D%2525%2526123%2521aZ%252B
> %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant
>
> this is dev.twitter.com example
> i saw it that oauth_signature is signature base string's hmac-sha1
> encoding and base64 encoding's result
> oauth_signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D"
> is it right?
> i can't do this.
> somebody help me. T.T
>
> Q1. i want to know signature base string's hmac-sha1 encoding result.
> Q2. oauth-signature="yUDBrcMMm6ghqBEKCFKVoJPIacU%3D" is it correct?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to