Hello, I'm using below library on my pure HTML client application for OAuth process. http://oauth.googlecode.com/svn/code/javascript/
I only use this library set and can't found problem on your token. my client app may help you if you're interest. mbtweet (only for Safari 4, Chrome and other WebKit browsers): http://taiyolab.com/mbtweet/about.html mbtweet github: http://github.com/ttrace/mbtweet On Fri, Feb 19, 2010 at 10:08 PM, Fernando Jorge <f.j.mot...@gmail.com> wrote: > Hello Andrew. > > I decided to use the JS OAuth-In-JavaScript (http://code.google.com/p/ > oauth-in-javascript/downloads/list), because it has already been made > to allow the use of OAuth in Firefox extensions . Signature is > generated in the critpografia HMAC-SHA1 and encrypted with the > standard RFC.Claro that, in the case of Twitter, I made some > modifications in order to apply the oauth_verifier among the > parameters, and even then only returns Twitter 401 Forbidden.Como I > tried to be in Abraham's PHP Lib, I have become the method used for > the request in GET.Abaixo I spend an example of the URL generated by > the script: > > https: / / api.twitter.com / oauth / access_token? oauth_consumer_key > = P3Ttvm4OXrCB4fTNY72xdw & oauth_nonce = > d41d8cd98f00b204e9800998ecf8427e & oauth_signature_method = HMAC-SHA1 > & oauth_timestamp = 1266584756 & oauth_token = > Hu22faLZe3iW6jonPzO0mDE1Q11Q8d0rIVJpy8hghA & oauth_verifier = 5575287 > & oauth_version = 1.0a & oauth_signature = 68XloBUImt3VHUqF3dzQpSDMPHQ > % 3D > > Detail: The signature is generated as if it were a normal request, but > it seems to be the problem, because Twitter only returns the 401 > Forbidden with nothing in its content. > > I await response. > > On 19 fev, 08:15, Andrew Badera <and...@badera.us> wrote: >> A 401 often indicates a poorly-formed signature. I would take the >> output of your JavaScript request and compare it visually with the >> output of a good reference implementation, like Abraham's lib. >> Sometimes it's hard to predict exactly what your output will look like >> when trying to port across platforms/languages, even if the logic >> appears correct. >> >> Also, consider taking a dependency on a known good reference JS >> implementation, like the one found on Google Code: >> >> http://code.google.com/p/oauth/source/browse/#svn/code/javascript >> >> ∞ Andy Badera >> ∞ +1 518-641-1280 Google Voice >> ∞ This email is: [ ] bloggable [x] ask first [ ] private >> ∞ Google me:http://www.google.com/search?q=andrew%20badera >> >> On Thu, Feb 18, 2010 at 7:59 PM, Fernando Jorge <f.j.mot...@gmail.com> wrote: >> > Hello, my name is Fernando, I am a Brazilian and developed a >> > 'TwitterLib' JavaScript to be able to manage all the power of >> > Twitter.Eu used the OAuth login to perform (and to show the extension >> > name as the "From" in a tweet: D), but I have a problem in getting the >> > Access Token, or better explained, Twitter me returns "401 Forbidden". >> > I checked every line of code and found absolutely nothing that could >> > damage, having considered until the code of Abraham's done in PHP Lib >> > OAuth.The code function that captures the "access_token" and makes the >> > request is available on PasteBin:http://pastebin.com/m7f4aa5c5note >> > that the same code is in JavaScript, because that I need help in that >> > essentially no parte.Se find any fault, please return me and I can >> > pass the functions performed by this function. >> >> > Dwell (forward) returns. >> >> > Detail: The Request Token is normally captured for information of all. >
