Is there any way to use OAuth and OpenID while working with the development server? -- Thadeus
Hi, On 2010-05-17 12:48 AM, Thadeus Burgess wrote: > Is there any way to use OAuth and OpenID while working with the > development server? Sure, why not? As long as the identity server is available you want to sign in with there is no reason that should not work. The remote server (the identity server in OpenID speak) does not need to access your server at all. Neither does OAuth for client applications. If you want to work offline however, you better install an openid identity provider application locally. There are probably some available on the intertubes :) Regards, Armin
I see. Twitter was sending me a 401 status code, but it was just that I set my application as type desktop instead of browser, switched to browser and gave the 127.0.0.1 for a return url and it works fine now. -- Thadeus On Sun, May 16, 2010 at 6:00 PM, Armin Ronacher <armin.ronacher@active-4.com> wrote: > g as the identity server is available you want to > sign in with there is no reason that should not work. The remote server > (the identity server in OpenID spe
Hi, On 2010-05-17 1:10 AM, Thadeus Burgess wrote: > I see. Twitter was sending me a 401 status code, but it was just that > I set my application as type desktop instead of browser, switched to > browser and gave the 127.0.0.1 for a return url and it works fine now. Indeed. You have to make sure that PIN based authentication is not activated for OAuth. To be honest, for anything else but command line tools, PIN based authentication is useless because even in a desktop application you would use the HTTP based one with an embedded browser control (Webkit or Trident). I wonder why Desktop app is the default in Twitter. Regards, Armin
After testing I had set Browser, i just didn't place anything in callback since I was working off the development server... and so it reverted to Desktop since I had not specified a default callback url. -- Thadeus On Sun, May 16, 2010 at 6:44 PM, Armin Ronacher <armin.ronacher@active-4.com> wrote: > Hi, > > On 2010-05-17 1:10 AM, Thadeus Burgess wrote: >> I see. Twitter was sending me a 401 status code, but it was just that >> I set my application as type desktop instead of browser, switched to >> browser and gave the 127.0.0.1 for a return url and it works fine now. > Indeed. You have to make sure that PIN based authentication is not > activated for OAuth. To be honest, for anything else but command line > tools, PIN based authentication is useless because even in a desktop > application you would use the HTTP based one with an embedded browser > control (Webkit or Trident). > > I wonder why Desktop app is the default in Twitter. > > > Regards, > Armin >