OAuth credentials are verified by default. If you have tokens that
work with Twitter, you know you have valid credentials. If that token
fails during a call, you must ask the user to reapprove with a new
token. There is never a need to verify credentials on the OAuth side
of the fence -- you always knew (or should know, record when grabbed)
whose OAuth token you have.
∞ Andy Badera
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
On Thu, Aug 27, 2009 at 3:29 PM, Gustavo Melo wrote:
> I was trying to change my old app for the new OAuth authentication.
>
> I'm using .NET C#
>
> I could get my token and tokenSecret. Ok.
>
> So i try to test verify_credentials.xml
>
> looks like this:
> http://twitter.com/account/verify_credentials.xml
> ?oauth_consumer_key=xx
> &oauth_nonce=xx
> &oauth_signature_method=HMAC-SHA1
> &oauth_timestamp=1251398498
> &oauth_token=xx
> &oauth_signature=%2bgUJx2ydmVWdoLgdGrFWfwy0efg%3d
>
> And i received this message:
> Could not authenticate you.
>
> But...
> If i put this link directly on browser some message box appear with:
> The API requer a login and password
> Login:
> Password:
>
> If a put my pass and login i can get the right return:
>
> X
> pipocadr
> pipocadr
>
>
> −
>
> http://a3.twimg.com/profile_images/299177807/3D_normal.png
>
>
>
>
> This is the basic auth or oauth? I pass my token and tokenSecret and
> consumerKey etc...
> So how can i get the result?
>
> Best Regards
>
