Hi Tom, Thanks for your email back..
I managed to get it sorted in the end.. Not entirely sure since I was cursing quite a bit, but hopefully by the end of today I'll have a full REALStudio (REALBasic) oAuth class..! Thanks Andy On 31 Jul 2010, at 01:50, Tom wrote: > I don't immediately see what's wrong, but consider tracing your steps. > > You already have a class that creates the authorization header. Feed > it some information which you know to be correct, and check for the > outcome. > > You could use these: http://dev.twitter.com/pages/auth#request-token - > all information is there, including values which you get between the > steps. > > Tom > > > On Jul 30, 11:46 am, Andy Dixon <andy.di...@zxcreative.com> wrote: >> Hello, >> >> I'm trying to migrate my code across to using oAuth, and there is no class >> for oAuth in the language I use, so I'm having to drop in at the deep end. >> >> At the moment, I am a bit stuck, I keep getting a 401 when I request a token. >> >> I have created this as my signature base string: >> >> POST&https%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%3DAXpCOWR4c2IZVlSGNXvdZg%26auth_nonce%3DQP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk%26auth_signature_method%3DHMAC-SHA1%26auth_timestamp%3D1280511571%26auth_version%3D1.0 >> >> Created a signed hash of this, using my Consumer Secret >> >> Base-64 encoded the hash since it was non-unicode >> >> URL Encoded the Base-64 string >> >> which then gives me: >> >> oAuth oauth_nonce="QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk", >> oauth_callback="oob", oauth_signature_method="HMAC-SHA1", >> oauth_timestamp="1280511571", oauth_consumer_key="AXpCOWR4c2IZVlSGNXvdZg", >> oauth_signature="4zCns2DZTQzmo2HpYY99dhJVl5A%3D", oauth_version="1.0" >> >> But when I make the POST request with the above set, I still get a 401 >> Unauthorised. >> >> Could someone steer me in the right direction please? >> >> Thanks :) >> >> Andy
