Skip to content

Add google oauth#77

Open
aymashaly wants to merge 7 commits into
devfrom
add-google-oauth
Open

Add google oauth#77
aymashaly wants to merge 7 commits into
devfrom
add-google-oauth

Conversation

@aymashaly
Copy link
Copy Markdown

Integrates Google authentication using next-auth v5, updates UI for Google sign-in in login and signup pages, and adds a new profile page. Includes backend route for extension authentication, updates header for user session management, and refines authOptions for Google provider and user handling. Also updates extension popup and styles for Google sign-in support.

Integrates Google authentication using next-auth v5, updates UI for Google sign-in in login and signup pages, and adds a new profile page. Includes backend route for extension authentication, updates header for user session management, and refines authOptions for Google provider and user handling. Also updates extension popup and styles for Google sign-in support.
Eliminated explicit NextAuthOptions type annotations from authOptions exports and imports, relying on type inference instead. Added 'as const' assertions for certain string values to improve type safety.
Introduces Google and Apple OAuth login options across the app and extension, including UI updates for login/signup pages and extension popup. Updates NextAuth configuration to support OAuth providers, refactors Prisma schema for SQLite, and adds a profile page. Temporarily disables Hotjar and Google Analytics scripts for debugging.
Deleted layout.tsx and profile/page.tsx from the caramel-app, removing the root layout and user profile functionality. This may be part of a refactor or migration to a new structure.
@dokploy-devinosolutions
Copy link
Copy Markdown

dokploy-devinosolutions Bot commented Sep 20, 2025

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
NextJS ❌ Failed Preview URL 2025-09-20T02:08:37.960Z

@dokploy-for-aladdin
Copy link
Copy Markdown

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: aymashaly
  • Repository: caramel
  • Permission Level: read
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.


This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants