jaredhanson / jaredhanson/passport
Maintaining Cross Domain session with passport.js
- Dominant language
- JavaScript
- Stars
- 23.5k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
I am using nodeJs for server and with express and passport as authentication middleware. My front end app is running on angular on localhost:9000 and node app on localhost:3000 . I found that the passport is not able to save session in cross domain . on every page request on my client app , passport create a new session for me instead of maintaining a single session . Also after login on login page it create a session in mongo with user detail available in it , but on second request it never resolve the same session cookie for me .
Contributor guide
Research direction
Start by reproducing the reported setup with the Angular app on localhost:9000 and the Node/Express app on localhost:3000, then inspect how the session cookie is handled after login and on the second request. Done means the existing Mongo-backed session is resolved consistently instead of a new session being created for each request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, express, javascript, mongodb, node.js
- Domain
- authentication, backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100