Indeed those do seem out of date, however they are mentioned here
http://dev.twitter.com/pages/auth
On Dec 8, 8:49 pm, Tim Bull wrote:
> Dave-tweinds,
>
> It is mentioned in passing and buried in some documents which discuss
> the full flow, but if you're relying on Twitter's own API
> documenta
Dave-tweinds,
It is mentioned in passing and buried in some documents which discuss
the full flow, but if you're relying on Twitter's own API
documentation (http://dev.twitter.com/doc/post/oauth/access_token)
you'll not see a single mention of the oauth_verifier here. Nor will
you see oauth_callb
Thanks Tim and Dave. It was not very clear in the docs, but I looked
at the latest docs from the library I use (from jmathai) and I did
find that he documented how to use this. I am up and running now from
multiple domains.
thanks,
Mark
On Dec 8, 4:07 am, Dave-twiends wrote:
> Hi Tim, I'm prett
Hi Tim, I'm pretty sure the oauth_verifier is documented in their
oAuth articles.. I'm speeking from memory here, but I'm sure I saw
last week when we were investigating our own oAuth issues..
But, nonetheless, you are correct, oauth_verifier should be passed
back every time.
Dave
Twiends
On Dec
There is a required OAuth parameter step which is unclearly documented
by Twitter. When Twitter returns from your /oauth/authorize It returns
an oauth_verifier token. Make sure that you pass this oauth_verifier
token (along with the other parameters) along to
your /oauth/access_token call.
Make s
Thanks for reply.
Kindly id like to discuss about this with some inline comments.
On Sep 8, 4:30 am, Matt Harris wrote:
> This is a known quirk of how that page works.
> If you don't provide a callback URL we default you back to a client
> application.
Without any notification ?!?!?
> To be a
This is a known quirk of how that page works. If you don't provide a
callback URL we default you back to a client application. To be able
to have a browser based application the callback URL must be
specified. When doing this remember you should still send a
oauth_callback during the request_token
Thanks Tom.
well, I choose the Browser as Application Type.
But I left the callback url field blank and it saved my settings
nicely ! and then when i checked it back the application type was
changed to client !!
and this time i wrote something in callback url field and seems it
really saved m
Ok, this one might be useful for others as well. The application was
registered as a client instead of a browser app. My app is an iPhone
app but it uses the browser for the OAuth part, so it should have been
browser type. Created a new app with the type set to browser and it
works fine now.
On Ju
I was under the impression that although oauth_callback is in the
OAuth standard, this parameter is not implement by Twitter.
I create multiple apps for development, staging, and live - and
maintain seprate deployment configs with the respective keys.
If that's true, then that would make testing/development very
difficult, if not impossible.
On Nov 25, 4:04 am, jmathai wrote:
> Without having tested it, I wouldn't be surprised if the callback url
> needs to be on the same domain as the url specified in application
> settings.
>
> Have you tr
Without having tested it, I wouldn't be surprised if the callback url
needs to be on the same domain as the url specified in application
settings.
Have you tried using a callback url to a random page on the domain of
the application setting url?
On Nov 24, 5:38 pm, Duane Roelands wrote:
> Trying
I don't remember off the top of my head but i want to say:
Encode the callback url: "http%3A%2F%2Frr.mydomain.com%3A7070%2Ftcallback.jsp"
Include the name=value *befor* signing:
"oauth_callback%3Dhttp%3A%2F%2Frr.mydomain.com%3A7070%2Ftcallback.jsp"
If that does not work I'll dig through my code
Look at the request_token request:
http://twitter.com/oauth/request_token?
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2ww&
oauth_nonce=nbmDOERzh6O&
oauth_signature_method=HMAC-SHA1&
oauth_timestamp=1246057852&
oauth_version=1.0&
oauth_signature=
There is no oauth_callback present.
Abraha
Oh you meant, we should add oauth_callback to request_token call
itself. I had actually tried that earlier, but i get "Failed to
validate oauth signature and token" :(
I also tried to use it as a part of generating signature, even that
didnt work. One other thing I tried is to change the version
Thats exactly what I think I am doing, am I not?
request_token(before encoding)...
http://twitter.com/oauth/request_token?oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2ww&oauth_nonce=nbmDOERzh6O&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1246057852&oauth_version=1.0&oauth_signature=
for authorize
When you get the request token add
"oauth_callback%3Dhttp%3A%2F%2Frr.mydomain.com%3A7070%2Ftcallback.jsp"
and when you send the user for authorization only include oauth_token.
Abraham
On Fri, Jun 26, 2009 at 16:55, goodtest wrote:
>
> I am using javascript and proxy to basically make request_to
http://us2.php.net/manual/en/oauth.getrequesttoken.php
On Sun, Jun 21, 2009 at 10:27 AM, Petermdenton wrote:
>
> Cool! Thanks for the reply.
>
>
> On Jun 21, 2009, at 12:24 AM, Abraham Williams <4bra...@gmail.com> wrote:
>
>
>> The bad news: Currently there is no way of doing this without editing
Cool! Thanks for the reply.
On Jun 21, 2009, at 12:24 AM, Abraham Williams <4bra...@gmail.com>
wrote:
The bad news: Currently there is no way of doing this without editing
the library to send oauth_callback with the initial request/etc.
The goood news: I'm almost done with a new version th
The bad news: Currently there is no way of doing this without editing
the library to send oauth_callback with the initial request/etc.
The goood news: I'm almost done with a new version that supports oauth_callback.
Abraham
On Wed, Jun 17, 2009 at 16:53, Peter Denton wrote:
> Hey,
> Can a few P
20 matches
Mail list logo
