[TASK-3] Create a login page for IIITBuzz .

[iamanishx]

🚀 Feature: Login Page with Google OAuth 2.0 (Backend-Based)

We need to implement the Login page for IIITBuzz, following the design that has already been finalized in the UI/UX phase. This page will be accessible via the /login route and serve as the central entry point for user Login/Signup via Google OAuth 2.0.

---

✅ Requirements

• The login should not use the Google Sign-In SDK (google.accounts.id) on the frontend.
• OAuth 2.0 flow should be implemented using a backend-based (Authorization Code) approach.
• After successful login:
  • The backend will verify the token using Google’s API.
  • Create or update the user in the database.
  • Issue a JWT to the client for session management.

---

📂 Expected Flow

1. User clicks Login with Google on the /login page.
2. The frontend redirects the request to the backend login endpoint to initiate the OAuth flow.
3. The backend redirects the user to Google’s OAuth consent screen.
4. Upon successful login, Google redirects to the backend callback URL.
5. The backend verifies the auth code and retrieves user info.
6. The backend creates/updates the user in the DB and returns a JWT.
7. The frontend stores the JWT securely (e.g., in HttpOnly cookie or secure localStorage) and redirects the user to the app dashboard.

---

🔒 Security Considerations

• No usage of Google JavaScript SDK on the frontend.
• All tokens and client secrets will be handled securely in the backend.
• Ensure CSRF and XSS protection while storing tokens.

---

🔗 References

• Google OAuth 2.0 Documentation

---

Feel free to discuss implementation details or suggest changes in the comments.

[burgerphilic18]

the entire login page is supposed to have only 1 button "Sign in with google" or there will be text boxes for username and password logins? since the additional details page is expected to be a different route in TASK 4, i was confused what to keep in login page

[iamanishx]

the entire login page is supposed to have only 1 button "Sign in with google" or there will be text boxes for username and password logins? since the additional details page is expected to be a different route in TASK 4, i was confused what to keep in login page

it will have just sign in with google