Implement OAuth Authentication (GitHub & Google) and Email/Password Login, Registration Page and Login Page #114
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.
Description
This PR introduces GitHub OAuth, Google OAuth, and email/password authentication methods across both the frontend and backend.
Frontend:
Backend:
Database:
Related Issue
#108
Motivation and Context
This change introduces multiple authentication options to make the application more flexible and secure. By adding OAuth integrations for GitHub and Google alongside the traditional email/password login, users can authenticate via their preferred method. This enhances user experience and makes the application more accessible.
Screenshots (In case of UI changes):
Login Page
Registration Page:
Types of changes
Checklist: