Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

clarify “It is not recommended using both this middleware and connect's built-in session middleware” #107

Open
Mithgol opened this issue Dec 22, 2015 · 0 comments
Open

clarify “It is not recommended using both this middleware and connect's built-in session middleware” #107

Mithgol opened this issue Dec 22, 2015 · 0 comments

Comments

@Mithgol
Copy link

Mithgol commented Dec 22, 2015

README.md currently says the following:

It is not recommended using both this middleware and connect's built-in session middleware.

Could you clarify it further?

  • What does (or might) break if connect's built-in session middleware is used with Mozilla's?
  • Is it safe to use express-session? Unfortunately, Passport's OAuth-based login strategies (e.g. logging in with Twitter, with Facebook, with Google…) require that module.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Mithgol