Hey guys,
I'm having a few problems with the OAuth API and my browser-based app
- it's giving me PIN numbers at the /oauth/authorize page, even though
it's set to return to a callback in the OAuth settings - I've
rechecked my settings, and the application is definitely set as a
browser app.
I'm
, 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
On Jun 9, 4:47 pm, Elliott
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
as if they shouldn't be there
anyways, correct?
On Jun 9, 5:28 pm, Elliott Kember elliott.kem...@gmail.com wrote:
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
.
If they want to log in as another user, they have to log out of
Twitter - the same way I have to log out of Google to use a different
OpenID account.
On Mar 27, 3:23 pm, Chad Etzel jazzyc...@gmail.com wrote:
On Thu, Mar 26, 2009 at 7:30 PM, Elliott Kember
elliott.kem...@gmail.com wrote:
If you don't
:
If they have to log in before you request authorization, can't you
just store the token with the login credentials (in your db) and use
it next time?
G.
On Mar 25, 8:19 pm, Elliott Kember elliott.kem...@gmail.com wrote:
Well, I've had it working for a while now using Rails. All
that thinks this could be really cool? What are the
downsides?
On Mar 26, 5:07 pm, Graeme Foster grae...@gmail.com wrote:
2009/3/26 Elliott Kember elliott.kem...@gmail.com
No - they don't log in before I request authorization. I get their
access token without having any idea who
Well, I've had it working for a while now using Rails. All this
solution needs is an Always authorize this app button.
The way I do it is: I request an OAuth token, and then call
verify_credentials with it to find out who they are. It seems to work
fine, except it forces the user to click Allow
Hi Graeme,
I think I'm doing a similar thing - I want to use Twitter as the
registration and login process for my app. Right now, Twitter asks for
approval every time the user logs into the account. Is there a way to
say remember this application and then always accept auth requests
from that
