Feature Request
Problem Statement
Currently Inquira only supports email/password authentication.
Adding Google OAuth would make it significantly easier for users
to sign up and log in — reducing friction during onboarding.
Proposed Solution
Add Google OAuth 2.0 as an authentication option alongside
the existing email/password flow.
Frontend changes
- Add "Continue with Google" button on Login and Register pages
- Handle OAuth redirect and token exchange
- Store JWT token same as existing auth flow
Backend changes
- Install
passport and passport-google-oauth20
- Add Google OAuth strategy
- Add routes:
GET /api/auth/google — redirect to Google
GET /api/auth/google/callback — handle callback
- On first login: auto-create user and organization
- On subsequent logins: return existing user JWT
Database changes
- Add
googleId field to User model in Prisma schema
- Make
password field optional (Google users won't have one)
Environment variables needed
GOOGLE_CLIENT_ID=your_google_client_id
GOOGLE_CLIENT_SECRET=your_google_client_secret
GOOGLE_CALLBACK_URL=https://your-backend-url/api/auth/google/callback
Implementation Steps
- Create Google OAuth app in Google Cloud Console
- Update Prisma schema — add
googleId, make password optional
- Install passport packages in backend
- Add Google OAuth strategy and routes
- Update Login and Register pages with Google button
- Test full OAuth flow
Acceptance Criteria
Labels
enhancement, auth, frontend, backend
Feature Request
Problem Statement
Currently Inquira only supports email/password authentication.
Adding Google OAuth would make it significantly easier for users
to sign up and log in — reducing friction during onboarding.
Proposed Solution
Add Google OAuth 2.0 as an authentication option alongside
the existing email/password flow.
Frontend changes
Backend changes
passportandpassport-google-oauth20GET /api/auth/google— redirect to GoogleGET /api/auth/google/callback— handle callbackDatabase changes
googleIdfield to User model in Prisma schemapasswordfield optional (Google users won't have one)Environment variables needed
GOOGLE_CLIENT_ID=your_google_client_id
GOOGLE_CLIENT_SECRET=your_google_client_secret
GOOGLE_CALLBACK_URL=https://your-backend-url/api/auth/google/callback
Implementation Steps
googleId, makepasswordoptionalAcceptance Criteria
Labels
enhancement,auth,frontend,backend