Unlocking the power of NextAuth by incorporating wild card or custom domains into the signin logic

Question

Unlocking the power of NextAuth by incorporating wild card or custom domains into the signin logic

My NextJS application is a multi-tenant SaaS application where each customer can choose to use a subdomain on our site or map their custom domain via CNAME.

This setup allows customers to enable their employees to log in on either the subdomain site or custom domain.

Within the [...nextauth].js file, there is a signIn callback that executes after sign-in:

async signIn({ user, account, profile, email, credentials }) {
 return true
},

In this callback, I need to determine which custom domain or subdomain the user is signing in from and apply specific logic accordingly. However, as the callback does not have access to req headers, how can I retrieve the domain/hostname within it? Depending on the domain, my goal is to permit/block signin or trigger other actions.

javascript next.js next-auth

Answer 1

Answer №1

Based on your query, the relevant section of the NextAuth documentation that addresses your specific use case can be found here:

https://next-auth.js.org/configuration/initialization#advanced-initialization

If you define a variable in this manner, it will be accessible within the NextAuth options too, as they share the same scope.

import NextAuth from "next-auth"
import { NextApiRequest, NextApiResponse } from "next"

export default async function authenticate(req: NextApiRequest, res: NextApiResponse) {
  const { host } = req.headers; 
  // utilize the value of 'host' in the NextAuth configuration below

  return await NextAuth(req, res, {
    // ...
  })
}

UPDATE:

To access NextAuth configuration in API routes or getServerSideProps, you can follow this pattern:

import { IncomingMessage } from "http";
import { NextApiRequest, NextApiResponse } from "next";
import NextAuth, { NextAuthOptions } from "next-auth";

export function authenticationOptions(req: IncomingMessage): NextAuthOptions {
  const { host } = req.headers;

  return {
    // ...
  }
};

export default async function authenticate(req: NextApiRequest, res: NextApiResponse) {
    return await NextAuth(req, res, authenticationOptions(req));
}

import { getServerSession } from "next-auth";
import { NextApiRequest, NextApiResponse } from "next";
import { authenticationOptions } from "./auth/[...nextauth]";

export default async function post(req: NextApiRequest, res: NextApiResponse) {
  const session = await getServerSession(req, res, authenticationOptions(req));
  // ...
}

Answer 2

Based on your query, the relevant section of the NextAuth documentation that addresses your specific use case can be found here:

https://next-auth.js.org/configuration/initialization#advanced-initialization

If you define a variable in this manner, it will be accessible within the NextAuth options too, as they share the same scope.

import NextAuth from "next-auth"
import { NextApiRequest, NextApiResponse } from "next"

export default async function authenticate(req: NextApiRequest, res: NextApiResponse) {
  const { host } = req.headers; 
  // utilize the value of 'host' in the NextAuth configuration below

  return await NextAuth(req, res, {
    // ...
  })
}

UPDATE:

To access NextAuth configuration in API routes or getServerSideProps, you can follow this pattern:

import { IncomingMessage } from "http";
import { NextApiRequest, NextApiResponse } from "next";
import NextAuth, { NextAuthOptions } from "next-auth";

export function authenticationOptions(req: IncomingMessage): NextAuthOptions {
  const { host } = req.headers;

  return {
    // ...
  }
};

export default async function authenticate(req: NextApiRequest, res: NextApiResponse) {
    return await NextAuth(req, res, authenticationOptions(req));
}

import { getServerSession } from "next-auth";
import { NextApiRequest, NextApiResponse } from "next";
import { authenticationOptions } from "./auth/[...nextauth]";

export default async function post(req: NextApiRequest, res: NextApiResponse) {
  const session = await getServerSession(req, res, authenticationOptions(req));
  // ...
}

Unlocking the power of NextAuth by incorporating wild card or custom domains into the signin logic

Answer №1

Similar questions

Reduce the size of static-generated assets using Next.js

The POST request functions smoothly in Postman, however, encounters an error when executed in node.js

JavaScript - undefined results when trying to map an array of objects

Error encountered in vscode: certain files failed to transfer during rsync process (code 23)

The computed function in Vue.js fails to provide a return value

What's the best way to align three images in a row?

Using AngularJS to pass the output of a unique filter to another custom filter

Regular expression that matches a string with optional leading and trailing spaces and a hyphen in the middle

What is preventing Javascript from executing a function when there is an error in another function?

Incorporating a HTML layout with a JS backdrop

What is the solution to fixing the Vue 2 error when using Node 12?

Refreshing HTML content using event delegation in JavaScript

Updating the state of Formik

Encountering a problem when looping through a JSON response

Tips for accessing req.fields variables while utilizing Express-Formidable

Is it possible to create a dynamic <hr /> using Flexbox?

Transferring data from a callback function within a component to a different component

Node JS: Despite modifying the URL, the response remains unchanged

I would greatly appreciate some guidance on asp.net and javascript

How can you use jQuery to target a textbox based on its value that includes quotation marks?