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

Implementing jwt with passport-local and not passport-local-mongoose #3

Open
itsyogesh opened this issue Jan 12, 2015 · 1 comment
Open

Comments

@itsyogesh
Copy link

Hey Rob,

I am trying to implement jwt with passport local and not with passport-local-mongoose, but I am not able to understand the flow. Taking this boilerplate, is there any way I can implement that. The reason why I am using this is because I might switch from passport-local to passport-basic since it allows for headers based user details and that I feel is more suitable for rest calls.

@roblevintennis
Copy link
Owner

@yogeshkumar180592 sorry I haven't touched this repo for a long time and I don't have time to dig in :( best of luck and sorry I can't be more helpful

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