cookieName, client-session and passportjs about node-client-sessions HOT 7 CLOSED

If you want to make the cookie name and the property name on request
different, you can use both cookieName and requestKey options. Set
cookieName to whatever you want, and requestKey to 'session'.
On Nov 22, 2013 6:13 AM, "yalamber" [email protected] wrote:

Hello,
I have seen that we can set cookieName to anything we want in this
library.
and access it with req.cookieName now will this work with passportjs? can
we set req.session directly with this library?

I am trying to implement client-session to work with passportjs. What
would be the recommended configuration?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/70
.

from node-client-sessions.

Hello,
So if change requestKey to session it should work properly with pasport.js right?

from node-client-sessions.

I assume so, but I've never used passport. The name you pass for requestKey
is the name you will access on request.

If requestKey='session', it will be req.session.
If requestKey='foobar', it will be at req.foobar.

from node-client-sessions.

It seems like it won't work with passportjs. Default cookieSession middleware works whereas node-client-sessions does not work. Is this issue with node-client-session or passportjs?

from node-client-sessions.

does it relate to this issue #42 ?

from node-client-sessions.

I did following change in passportjs jaredhanson/passport#185
And it seems to work now. Should I be careful implementing this patch?

from node-client-sessions.

@yalamber yes, this would work better with passport if #42 were fixed. I'm working on that.

from node-client-sessions.