Same issue here.  The username/password version of my client works, but not
the oAuth version.  It just times out when redirecting back.  It's weird
because some of my users can get through, but none of my accounts can.

On Thu, Aug 6, 2009 at 5:00 PM, Sam Street <sam...@gmail.com> wrote:

>
> My app also dies straight during auth http://twicli.com/auth
>
> On Aug 6, 10:45 pm, Rich <rhyl...@gmail.com> wrote:
> > Especially annoying seeing as I've gone totally oAuth now.  I don't
> > blame Twitter, just the idiots that initiated the DDoS attack
> >
> > On Aug 6, 10:33 pm, Andreu Pere <andreup...@gmail.com> wrote:
> >
> > > The same behaviour for my application. When the app wants to start the
> oAuth
> > > workflow in order to authenticate and login the user, the server
> returns a
> > > timeout fromhttps://twitter.com/oauth/authenticate?parameters
> >
> > > On Thu, Aug 6, 2009 at 11:24 PM, Rich <rhyl...@gmail.com> wrote:
> >
> > > > I can't get oAuth to authenticate on any of my clients either.  It
> > > > works when the client has previously authenticated... but trying to
> > > > get a new token it fails when clicking 'Allow'
> >
> > > > On Aug 6, 7:42 pm, stephane <stephane.philipa...@gmail.com> wrote:
> > > > > It's probably linked to the current DDOS but the authentication
> flow
> > > > > shows some strange behavior :
> >
> > > > > 1 - I try to initiate an OAuth authentication fromwww.twazzup.com
> > > > >   <- twazzup server gets a timeout trying to connect to twitter for
> > > > > oauth token (ApplicationError 5 on appengine)
> > > > > 3 - I go to twitter.com click "sign-in"
> > > > >   <- strangely twitter redirects me to the oauth authorization form
> > > > > (do you want to allow twazzup blabla ...)
> >
> > > > > So I have to questions there :
> > > > > A / did you block incoming OAuth reqs from appengine ?
> > > > > B/ is the strange behavior (twitter home authentication mixing with
> > > > > another OAuth flow) something we, 3rd party app developers, can or
> > > > > should take care of ?
> >
> > > > > Cheers,
> >
> > > > > Stephanewww.twazzup.com
>

Reply via email to