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.

Sign up for GitHub

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

Jump to bottom

deserializeUser is not called when session was not found in DB. Is it correct behavior? #161

Open
wzup opened this issue Oct 10, 2017 · 0 comments
Open

deserializeUser is not called when session was not found in DB. Is it correct behavior? #161

wzup opened this issue Oct 10, 2017 · 0 comments

Comments

@wzup
Copy link

wzup commented Oct 10, 2017 •
edited
Loading

I discovered that deserializeUser is not called if session was not found in a DB by express-mysql-session. Is it correct behavior?

Use case:

I'm using passport-local with session = true and with express-mysql-session as a session store. When session is ok (found by express-mysql-session in a DB) then deserializeUser is called all right. However if a session for some reason isn't found in a DB (eg. session cookie is manually deleted in a browser or a session row is manually deleted from DB) then deserializeUser doesn't get called. Why? Is it correct behavior?
@wzup wzup changed the title deserializeUser is not called when session was deleted. Is it correct behavior? deserializeUser is not called when session was not found in DB. Is it correct behavior? Oct 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wzup