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

Why passport.serializeUser and deserializeUser is being used? #17

Open
fega opened this issue May 8, 2018 · 2 comments
Open

Why passport.serializeUser and deserializeUser is being used? #17

fega opened this issue May 8, 2018 · 2 comments

Comments

@fega
Copy link

fega commented May 8, 2018

No description provided.

@fega
Copy link
Author

fega commented May 8, 2018

I would like to know how is i being handled in the flow, I'm seeing that all the uses of authenticate is using "{session:false}"

thanks

@ksmithut
Copy link

ksmithut commented Sep 6, 2018

All of the token based endpoints are used that way because those won't be session based. The user will be retrieved via the oauth flow. But this line: https://github.com/gerges-beshay/oauth2orize-examples/blob/master/routes/site.js#L10 shows that when a user is signed in locally to the oauth2 server, it will save a session so the user doesn't have to enter their credentials.

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

2 participants