NextAuth 4 (Next.js 13) Fails in Iframe – Redirect Loop, Possible Header Issue?

[SmileHub]

Hello,
I'm experiencing an issue with NextAuth.js (v4) in a Next.js 13 app when the site is embedded in an iframe.

✅ Expected Behavior: Login should work the same inside and outside an iframe.
❌ Actual Behavior: When embedded in an iframe, users get redirected back to the login page after attempting to sign in. Outside the iframe, login works fine.

Debugging Attempts:

1. Identified a possible issue with the Referrer-Policy header

• Using Insomnia, I noticed that adding Referrer-Policy: strict-origin-when-cross-origin causes a 400 Bad Request from nginx when calling /api/auth/providers.
• Without this header, the request goes through fine.
• I suspect that NextAuth or Next.js is setting this header, causing login failure when embedded.

2. Tried modifying headers in Next.js via headers() API:

async headers() {
  return [
    {
      source: '/:path*',
      headers: [
        { key: 'Access-Control-Allow-Origin', value: '*' },
        { key: 'Access-Control-Allow-Methods', value: 'GET, POST, PUT, DELETE, OPTIONS' },
        { key: 'Access-Control-Allow-Headers', value: 'Content-Type, Authorization' },
        { key: 'Cross-Origin-Resource-Policy', value: 'cross-origin' },
        { key: 'Cross-Origin-Embedder-Policy', value: 'unsafe-none' },
      ],
    },
  ];
},

• However, this did not solve the issue.

3. Tried modifying iframe attributes to loosen restrictions:

<iframe content-security-policy="default-src * 'unsafe-inline' 'unsafe-eval';" referrerpolicy="unsafe-url" src="..."></iframe>

• No improvement.

4. Tried modifying the NextAuth API route to remove headers:

Initially, I tried modifying [...nextauth].ts to remove Referrer-Policy, but I wasn't sure if the function was executing.
However, after testing further, the function does apply, but now I get a new error even when not using an iframe:

[next-auth][error][CLIENT_FETCH_ERROR] 
https://next-auth.js.org/errors#client_fetch_error JSON.parse: unexpected character at line 1 column 1 of the JSON data 
Object { error: {…}, url: "/api/auth/session", message: "JSON.parse: unexpected character at line 1 column 1 of the JSON data", client: true }

Here’s the updated [...nextauth].ts function:

import type { NextApiRequest, NextApiResponse } from 'next';
import NextAuth from 'next-auth';
import { authOptions } from '../../../../utils/authOptions';

export default async function auth(req: NextApiRequest, res: NextApiResponse) {
  console.log('Auth API route hit');
  res.removeHeader('Referrer-Policy');
  delete req.headers['Referrer-Policy'];
  
  return await NextAuth(req, res, authOptions);
}

• The console log now appears, so the function is executing.
• However, I now get the CLIENT_FETCH_ERROR when NextAuth tries to fetch /api/auth/session.
• This happens even without an iframe.

Open Questions:

1. Why does NextAuth fail inside an iframe? Could it be related to cookies (SameSite policies) or the Referrer-Policy header?
2. Why does modifying [...nextauth].ts result in a CLIENT_FETCH_ERROR for /api/auth/session?
3. Is there a proper way to allow authentication to work inside an iframe without breaking NextAuth's session management?

Any help or suggestions would be greatly appreciated!

[ManuLpz4]

Same here, any news on this?

[SmileHub]

oh yes, added to NextAuthOptions:

cookies: {
		csrfToken: {
			name: `__Secure-next-auth.csrf-token`,
			// name: `__Host-next-auth.csrf-token`,
			options: {
				httpOnly: false,
				sameSite: 'none',
				path: '/',
				// secure: process.env.NODE_ENV === 'production',
				secure: true, //required with sameSite none
			},
		},
		sessionToken: {
			name: `__Secure-next-auth.session-token`,
			options: {
				httpOnly: false,
				path: '/',
				sameSite: 'none', // Required for iframes in cross-origin contexts
				// secure: process.env.NODE_ENV === 'production',
				secure: true, //required with sameSite none
			},
		},

also iframe origin settings had to be adjusted, gl