I've read that we must now attach the oauth_verifier to the request
for the access_token.
I'm a bit confused as to how to do this. Can anyone clarify?
Verified... I redefined the method to exclude the oauth_callback
default from being set and that returned the service to normal
function.
OAuth::Consumer.class_eval do
def get_request_token(request_options = {}, *arguments)
response = token_request(http_method, (request_token_url? ?
Quick fix/patch/hack for the Ruby OAuth gem - just load this after
the gem is loaded. A Rails initializer will work.
http://gist.github.com/127313
On Tue, Jun 9, 2009 at 7:20 PM, Matt Sanfordm...@twitter.com wrote:
Hi again,
Nobody is forcing you to use the PIN unless you're registered
Am 10.06.2009 um 18:14 schrieb Jonathan Otto:
Quick fix/patch/hack for the Ruby OAuth gem - just load this after
the gem is loaded. A Rails initializer will work.
http://gist.github.com/127313
I still have problems - even with this gist above!!
I'am using oauth-gem 0.35.
I always get a
Same here, actually, for tweetingtoohard.com (tried to post here
before but it looks like it got eaten :P)
We've put up a snarky message in the meantime about the blunders :P
But please do correct us if we have done something incorrect.
-- Keith Hanson
@big_love
keith (at) tweetingtoohard.com
Hey Matt,
Yep, I'm passing oauth_callback - and it does look like that's the
problem, because I have another app which doesn't send it, and it's
working fine.
Is this by design, or will it be changed back? I don't need it to use
the oauth_callback url that I pass, but it'd be good to return to
Sorry - having said that, I've removed the oauth_callback parameter
and the behaviour is still persisting - and it also doesn't save the
authentication so I have to hit Allow every time.
On Jun 9, 11:21 pm, Elliott Kember elliott.kem...@gmail.com wrote:
Hey Matt,
Yep, I'm passing
I'm actually not using an oauth callback parameter and am getting this
behavior.
I'm running on Sinatra at the moment, but have implemented my login
routine by pretty much copy/pasting the Rails tutorial in the API
Wiki.
I'm using the gem OAuth 0.3.5 for redirecting and what-not.
I did take a
I'm seeing exactly the same behaviour and it just started happening a
few hours ago
App is http://moodmapr.com
Users just cannot login but instead are provided with a PIN
On Jun 9, 11:37 pm, Keith Hanson seraphimrhaps...@gmail.com wrote:
I'm actually not using an oauth callback parameter
Hi there,
Are you by chance passing anything in to the request_token call
for the value of oauth_callback? I checked out a few other services
and they seemed fine. If you're sending oauth_callback=oob (a.k.a.
out of band) then the system is forced into the PIN flow. We're
working on
Hi there,
I just checked the tokens generated on several of these services
and I see oauth_callback was set to oob. Doug is working on the docs
right now to make it clear how all of this shakes out. The end result
is that if you want to use the pre-configured callback url don't send
Huzzah!
It looks like the OAuth gem, when not given the parameter
oauth_callback, automatically passes oob, FTL! :P
So... in our case, we simply did this:
consumer = OAuth::Consumer.new(TOKENZ, SECRETZ, { :site=http://
twitter.com })
consumer.get_request_token(:oauth_callback = http://
I have made little to no changes and this behaviour just started
happening this evening
Try logging in at http://moodmapr.com to see what happens
I have commented out all the lines of code that pass 'oauth_callback'
in the url on my development environment and it doesn't seem to make a
I also do not use oauth_callback and this is happening to me as well.
I have emailed a...@twitter.com and Doug Williams responded.
On Jun 9, 5:17 pm, Matt Sanford m...@twitter.com wrote:
Hi there,
Are you by chance passing anything in to the request_token call
for the value of
I managed to get the old behaviour back by modifying the oauth gem to
not set a default oauth_callback (oob)
For some reason the twitter-auth gem is not passing over the
configuration to override the default
I'm too tired to investigate further at the minute but will keep
looking in the morning
Surely this is all moot anyway - can't the OAuth process just redirect
if the application only accepts callbacks? We set a preference for
callbacks in the OAuth settings, so why are we being forced into PIN
verification?
On Jun 10, 12:46 am, lebreeze lebre...@gmail.com wrote:
I managed to get
Hi again,
Nobody is forcing you to use the PIN unless you're registered as
a desktop app (which has no callback). The issue here is that the
library you are using is setting a value of oob and specifically
requesting the PIN flow. I have filed an issue with the gem maintainer
on
17 matches
Mail list logo
