Cross domain authentication using nextjs

[Himasnhu-AT]

Goals

• Enable cross-domain authentication to provide a seamless user experience across multiple domains.
• Ensure secure cookie sharing for authentication, with default restrictions to the hosted domain for added security.
• Minimize backend complexity by integrating efficient authentication mechanisms directly into the application.
• Reduce reliance on external frameworks like Nest.js or nodejs, or any other backend framework, to save deployment costs, especially for student-focused projects.

Non-Goals

No response

Background

I have multiple applications, hosted on different domains, with different codebases. I want to keep a single auth route that is shared between all domains. Right now their no such way by default in the next-auth next auth

Proposal

Yes, I'm interested in contributing.

This approach aligns with my goals of upskilling, learning advanced authentication, and reducing backend deployment costs, as I’d otherwise need to rely on Nest.js, which isn't financially feasible for me as a student.

Heres a workaround i have in mind, but unsure if its great (for security):

To implement cross-domain authentication for my projects, we can leverage Next.js' cross-origin configuration to securely manage cookies and credentials across domains. Then modifying CORS policies, we can ensure that this API can be called from other domains and give seamless login experiences.

This functionality will help other user and projects if they are planning on implement this functionality