feat: Login Authentication#8
Open
CodingPhionix wants to merge 5 commits intoOpenSourceSprint:mainfrom
Open
Conversation
fix: issue OpenSourceSprint#5 - Added a controller to fetch all books from the database. - Used the Book model to retrieve book data from the database. - Returned the fetched books in the response along with a success message.
- Added a controller to handle book deletion by ID. - Utilized the Book model to find and remove the book from the database. - Returned a success message upon successful deletion of the book.
Updated the typos
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix-issue: #2 , #1 , #5, #7
Issue #1 :
I implemented a login route using Node.js and Express. The solution involved the following steps:
Validation: I validated the request body to ensure it contained the required fields, namely
emailandpassword.Authentication: I authenticated the user by checking if the provided email and password matched the credentials stored in the system.
JWT Token Generation: Upon successful authentication, I generated a JSON Web Token (JWT) containing the user's information and signed it with a secret key.
Response: Finally, I returned the JWT token along with a success message indicating that the user logged in successfully.
This approach ensures secure authentication and enables users to access protected routes using the issued JWT token.
Next I did was Issue #2 :
Issue #5 :
Issue #7 :