node.js - Passport.js / Express.js Creating New Session on Every Network Request -


i have working login function authenticates , saves. however, express never remembers old session, creates new 1 every network request.

evidently, passport exceedingly sensitive order express middleware initialized. (example: https://www.airpair.com/express/posts/expressjs-and-passportjs-sessions-deep-dive). checked config against number of examples , rearranged if help, hasn't moved bug. either isn't issue or haven't found config holy grail yet. here's current config:

express config

app.engine('html', require('ejs').renderfile); app.set('view engine', 'html'); app.use(express.static(path.join(config.root, '/views'))); app.set('views', config.root + '/views'); var sessionopts = {     saveuninitialized: true,     resave: false,     store: new redisstore({         host: 'localhost',         port: 6379     }),     secret: 'keyboard',     cookie: {         httponly: true,         maxage: 1000     } } app.use(bodyparser.json()); app.use(bodyparser.urlencoded({     extended: false })); app.use(cookieparser('keyboard')); app.use(session(sessionopts)); app.use(passport.initialize()); app.use(passport.session()); app.use(cors()); require('./routes/router.js')(app, passport);

passport config

 passport.use('local-login', new localstrategy({     usernamefield: 'email',     passwordfield: 'password',     passreqtocallback: true }, function(req, username, password, done) {     client.hgetall(username, function(err, reply) {         if (err) {             return done(err);         }         if (!reply) {             return done(null, false, {                 message: 'incorrect username.'             })         }         if (reply.password !== password) {             return done(null, false, {                 message: 'incorrect password.'             })         }         return done(null, reply)     }) }));

does passport need handholding redis? redis sessions stored in 'sess' folder key so: sess:rhodmak2v2wdnlglv5j1b6rc. of tutorials i've found have been mongo i'm not sure if need somehow include session key when trying up. within session entry, it's stored in standard cookie form passport though: req.session.passport.user

is there way see happening inside of passport initialize? on subsequent requests supposed this: "the general passport middleware setup (passport.initialize) invoked on request, finds passport.user attached session. if doesn't (user not yet authenticated) creates req.passport.user = {}." see 'subsequent authenticated requests flow' - http://toon.io/understanding-passportjs-authentication-flow/ suspect problem lies @ step, nice able see inside of it.

some interesting tidbits:

  • passport has never once called deserializeuser. assume it's never
    reached point.
  • i have checked other stackoverflow questions problem, none of solutions worked me.
  • i've checked see if new sessions generated static resources not. it's intentional server requests. on pages without them, no new sessions made.
  • all sessions have either populated or empty req.session.passport property.

your session id might different every request because have cookie set expire after 1 second. cookie.maxage here in ms:

cookie: {     httponly: true,     maxage: 1000 }

edit: have nag storing passwords in plaintext. don't ;)


-

Comments

Post a Comment

Popular posts from this blog

apache - PHP Soap issue while content length is larger -

we have developed soap based webservice post data third party webservice. accepts 4 params. in 1 of parameters accepts xml string no size limit restriction put in place. the webservice works fine in local environment running on php 5.2 , apache2. works content length long 10 mb. in staging server running nginx , php fpm.we have updated max post size , max upload filesize in php.ini , client_max_body param in nginx.conf allow upto 50 mb. but webservice client keeps on loading in staging environment. gives 502 timeout , gives soap error. can me understand issue here?
Read more

asynchronous - Python asyncio task got bad yield -

i confused how play around asyncio module in python 3.4. have searching api search engine, , want each search request run either parallel, or asynchronously, don't have wait 1 search finish start another. here high-level searching api build objects raw search results. search engine using kind of asyncio mechanism, won't bother that. # no asyncio module used here class search(object): ... self.s = some_search_engine() ... def searching(self, *args, **kwargs): ret = {} # raw searching according args , kwargs , build wrapped results ... return ret to try async requests, wrote following test case test how can interact stuff asyncio module. # here testing script @asyncio.coroutine def handle(f, *args, **kwargs): r = yield f(*args, **kwargs) return r s = search() loop = asyncio.get_event_loop() loop.run_until_complete(handle(s.searching, arg1, arg2, ...)) loop.close() by running pytest, return runtimeerror: task got bad yield : {results s...
Read more

javascript - Complete OpenIDConnect auth when requesting via Ajax -

the normal openidconnect server works like: you go a.com/secure-resource you 302 server your browser handles , sends identity server you login there it sends a.com via post you logged in on a.com , a.com/secure-resource on browser. however have scenario i'm trying solve need help. the user logged in on idserver the user logged in on a.com the user not logged in on b.com we need send ajax call web server b.com (from domain a.com ) b.com configured use openidconnect. but because request b.com via ajax, user cannot redirected idserver. (all in response 302 ) we can go ahead , handle 302 via ajax (i'm still not sure whether work, security-wise). but is there scenario in identityserver/openidconnect designed these situations? with identityserver in scenario setup server b.com use bearer token authentication, need use access token provided a.com in headers of ajax call $.ajax({ url: 'http://b.com', headers: { ...
Read more