Hey João,

The signing key is the concatenation of the
consumer_secret&user_secret. If you don't have a user_secret the
signing key will be consumer_secret&.

A couple of examples ....

consumer_secret: 1234
user_secret:
signing_key: 1234&

consumer_secret: 1234
user_secret: 5678
signing_key: 1234&5678


Give that a try and see it helps.
Matt

2010/8/31 João Paulo Sabino de Moraes <jona...@gmail.com>:
> thanks taylor,
> I'm using a newer as3 api, and lookint at its sorces I saw how to get
> oauth_signature only for oauth authentication and I'm trying to adapt it to
> xAuth.....
> I think my only problem is the way I'm calculating oauth_signature based on
> hmac ....
> as you can see at the 2 lines below
> var hmac:HMAC =  Crypto.getHMAC("sha1");
> var key:ByteArray = Hex.toArray(
> Hex.fromString(encodeURIComponent(consumerKey) + "&" +
> encodeURIComponent(consumerSecret)));
> I'm making a hmac key based on consumerKey and consumerSecret and here:
> var data:ByteArray = Hex.toArray( Hex.fromString( signString ) );
> var oauth_signature:String = Base64.encodeByteArray( hmac.compute( key, data
> ) );
> I'm encoding data (encoded base string) with consumerKey and secret hmac key
> and that would be my oauth_signature.
>
> So,I'm not sure if the way I'm calculating key var is correct....
> Concat encoded consumer key and consumerSecret is the right thing ?
> thanks
>
> --
> 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
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
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