i did manage to get xauth working this morning thanks to @SteveReynolds.  the 
big epiphany (Steve's, not mine) was that there is no token exchange at all.  
in fact you don't even seem to need to acquire a request token ever.  you 
simply jump directly to the auth token request and pass in your default token.

it seems to make sense to me now, it was just a leap that i didn't make on my 
own.

i just thought i'd post this in case anyone else out there is stuck too.


when it's a bit more cleaned up, i'll post my results to github.

isaiah
http://twitter.com/isaiah


On Feb 27, 2010, at 9:37 AM, Aral Balkan wrote:

> Like a n00b, I didn't include the id of my app in my original support request 
> (I hadn't registered it since I wasn't using oAuth previously) and so it 
> looks like I've missed the initial boat :( Got a message back asking for my 
> app id so I registered Feathers and got back to the ticket but apparently the 
> Twitter helpdesk/zendesk is down (http://help.twitter.com) so not sure if my 
> ticket was updated.
> 
> Would really appreciate it if anyone can look into the ticket (Ticket #863920)
> 
> Thanks :) 
> 
> Aral
> 
> On Sat, Feb 27, 2010 at 6:47 AM, Isaiah Carew <isa...@me.com> wrote:
> 
> So, I received the xAuth green light.  Yeah!!!
> 
> Unfortunately, the email was not very detailed about which app was enabled (I 
> have 3).  (and for the record I was very detailed in my request about which 
> one I was requesting access for).
> <snip>

Reply via email to