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).
So I gave it a shot. No dice. Seems to behave the same way as yesterday. So, now I've tried all three of my registered app credentials, just in case. Same 401 result. I've tried changing all the switches on the Twitter App configuration page. Then on all thee apps. Nope. Nope. Nope. Should the xauth parms be included in the "base string" for generating the signature? My guess is yes, but I couldn't find anything very conclusive after scouring the oauth spec and the xauth paper. I've tried both -- with all my apps -- with all the switches. Nope ^ 4. The number of ambiguous variables is pretty large here. Would anyone on the api team like to throw me a bone and tell me: - which app they enabled? - if there are specific settings on the App page that should be set or not set? (Client or Web? Login with Twitter?) - i'd really love to know the specifics about the xauth params and the signature. i'm sure it's in some doc somewhere -- a link to a page in a doc would be super. Just nailing down a few of those combinations will make the debug process a lot smoother. Currently I'm using an implementation that works very well pre-xauxth and is successfully getting request tokens without any problems. If I switch it over to PIN mode things seem to work well for all three apps of my Twitter apps. It generates the required headers, and exchanges request tokens for oauth tokens reliably. Unfortunately the error messages aren't very interesting: "401: Unauthorized." feel free to email for more techy details. i've got loads. ;-) isaiah http://twitter.com/isaiah
