-
Notifications
You must be signed in to change notification settings - Fork 45
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
JwtAuthAdded #55
JwtAuthAdded #55
Conversation
✅ Deploy Preview for hashide ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for hardcore-bardeen-855706 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@irshadmd sir, please review !! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes look good but some checks are failing, since the master is changed try to take pull from master and then re-create PR.
ISSUE #48
Added a field i.e token array to the userModel which holds the tokens.
Created a dummy protected route /user to show the implementation.
-When the user registers the token gets added to the tokens array
-When the user logs in the token is added to the tokens array
-If no token/incorrect token is provided with the auth-token key in the header of the protected route then the user is denied
access of that route
Correct token provided and thus the user is able to access the protected route
Please review @khareyash05 sir