jaredhanson / jaredhanson/passport
deserializeUser not triggering through browser, but working with postman
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 23.5k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
In my MEAN project, I have used passport authentication and calling login service from angular 5 service. When I hit the login service from browser I am getting success response but userdata coming as null, but userdata coming properly when I hit service through postman.
I have consoled in deserializeUser but this deserializeUser not triggering when I tried through browser.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the browser login request with the Postman request and trace the deserializeUser path described in the issue. Done means identifying why browser requests return null userdata while Postman requests do not, then verifying the browser flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript, node.js
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100