express 2 not working about connect-auth HOT 13 CLOSED

I'm having the same issue - and a similar one with the facebook example.

from connect-auth.

Ditto.

from connect-auth.

Same here

from connect-auth.

Same here with GitHub auth. It still works but the server eventually locks up.

from connect-auth.

i think your supposed to use res.end not res.send...

from connect-auth.

res.end worked.

from connect-auth.

I'm getting this with res.render but not with res.end

from connect-auth.

Implemented in 0.3.0

from connect-auth.

Haven't tested, but thank you.

from connect-auth.

I'm still having this issue as of 0.3.1

from connect-auth.

Which strategy.. I'm investigating an issue with the google strategy (google seem not to end their connections to json feeds anymore?) ... can you point me at your code at all ?

from connect-auth.

The facebook strategy ... I'm not sure if I'm supposed to be trying to redirect in there and whether or not that's what is causing it ...

app.get('/auth/facebook',function(req,res){
  req.authenticate(['facebook'], function(error, authenticated) {
    res.redirect('/');
  });
});

After thinking more about it ... what is likely going on here is that authenticate is sending the headers and I'm trying to add on to them with the redirect ... what is the suggested way to redirect after authenticating?

I ended up replacing it with a javascript redirect.

from connect-auth.

Ok. So presumably you want to call into loadAccount when a session first successfully authenticates?

The best place to do this is over in your express/connect app or in some middleware... I'd like connect-auth to track first-authenticate and logout as a set of callbacks/events .. but as this doesn't currently exist you just need to do it yourself ...
have you seen: https://github.com/ciaranj/connect-auth/wiki/Example-Basic-Middleware-Implementation-(Facebook) this gives a pretty full implementation of everything I think that you might need?

from connect-auth.