Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to serialize user into session #150

Open
Kran891 opened this issue Jun 14, 2023 · 0 comments
Open

Failed to serialize user into session #150

Kran891 opened this issue Jun 14, 2023 · 0 comments

Comments

@Kran891
Copy link

Kran891 commented Jun 14, 2023

Error: Failed to serialize user into session at pass (C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport\lib\authenticator.js:278:19) at serialized (C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport\lib\authenticator.js:283:7) at C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport-local-mongoose\index.js:212:7 at pass (C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport\lib\authenticator.js:291:9) at Authenticator.serializeUser (C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport\lib\authenticator.js:296:5) at C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\passport\lib\sessionmanager.js:33:10 at Immediate._onImmediate (C:\Users\krreddyg\OneDrive - Capgemini\Desktop\Secrets-Google Auth\node_modules\express-session\session\store.js:54:5) at process.processImmediate (node:internal/timers:478:21) ** READ THIS FIRST! **

Are you looking for help?

Reminder: The issue tracker is not a support forum.

Issues should only be filed in this project once they are able to be reproduced
and confirmed as a flaw in the software or incorrect information in associated
documention.

If you are encountering problems integrating this module into your application,
please post a question on the discussion forum
rather than filing an issue.

Is this a security issue?

Do not open issues that might have security implications. Potential security
vulnerabilities should be reported privately to [email protected]. Once any
vulerabilities have been repaired, the details will be disclosed publicly in a
responsible manner. This also allows time for coordinating with affected parties
in order to mitigate negative consequences.

If neither of the above two scenarios apply to your situation, you should open
an issue. Delete this paragraph and the text above, and fill in the information
requested below.

Expected behavior

Actual behavior

Steps to reproduce

// Format code using Markdown code blocks

Environment

  • Operating System:
  • Node version:
  • passport version:
  • passport-google-oauth version:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant