[Next.js] AuthRequiredError when calling Data API with createNeonAuth session token
Neon
Node.js❓QuestionI am using Next.js 15 (App Router). I need to securely query my Neon database from Server Actions with authentication.
I am using the official @neondatabase/auth and @neondatabase/neon-js packages. My approach is to retrieve the session using auth.getSession(), extract the token, and inject it as an Authorization: Bearer header into the global fetch options of the Data API client.
import { createNeonAuth } from "@neondatabase/auth/next/server";
export const auth = createNeonAuth({
baseUrl: process.env.NEON_AUTH_BASE_URL!,
cookies: { secret: process.env.NEON_AUTH_COOKIE_SECRET! },
});
import { createClient } from "@neondatabase/neon-js";
export async function getAuthenticatedDbClient() {
const sessionResponse = await auth.getSession();
const token = sessionResponse?.data?.session?.token;
if (!token) throw new Error("No valid token found in session.");
return createClient({
auth: { url: process.env.NEON_AUTH_BASE_URL as string },
dataApi: {
url: process.env.NEON_DATA_API_URL as string,
options: {
global: {
headers: { Authorization:
fetch: fetch,
},
},
},
});
}
Logs and Error Messages:
When executing a simple query the Data API rejects the request.
What I've already tried:
1. Passing the raw Next.js cookieStore.toString() directly into the cookie header of the Data API fetch options (failed).
2. Extracting the token from auth.getSession() and passing it as a Bearer token (my current approach, still failing).
3. Verifying all environment variables (NEON_AUTH_BASE_URL, NEON_DATA_API_URL, etc.) are correctly set.
My Question:
What is the recommended approach to link the session from createNeonAuth to the createClient Data API config? Does the Data API expect a different header format, am I missing a configuration step?
I am using the official @neondatabase/auth and @neondatabase/neon-js packages. My approach is to retrieve the session using auth.getSession(), extract the token, and inject it as an Authorization: Bearer header into the global fetch options of the Data API client.
import { createNeonAuth } from "@neondatabase/auth/next/server";
export const auth = createNeonAuth({
baseUrl: process.env.NEON_AUTH_BASE_URL!,
cookies: { secret: process.env.NEON_AUTH_COOKIE_SECRET! },
});
import { createClient } from "@neondatabase/neon-js";
export async function getAuthenticatedDbClient() {
const sessionResponse = await auth.getSession();
const token = sessionResponse?.data?.session?.token;
if (!token) throw new Error("No valid token found in session.");
return createClient({
auth: { url: process.env.NEON_AUTH_BASE_URL as string },
dataApi: {
url: process.env.NEON_DATA_API_URL as string,
options: {
global: {
headers: { Authorization:
Bearer ${token}fetch: fetch,
},
},
},
});
}
Logs and Error Messages:
When executing a simple query the Data API rejects the request.
What I've already tried:
1. Passing the raw Next.js cookieStore.toString() directly into the cookie header of the Data API fetch options (failed).
2. Extracting the token from auth.getSession() and passing it as a Bearer token (my current approach, still failing).
3. Verifying all environment variables (NEON_AUTH_BASE_URL, NEON_DATA_API_URL, etc.) are correctly set.
My Question:
What is the recommended approach to link the session from createNeonAuth to the createClient Data API config? Does the Data API expect a different header format, am I missing a configuration step?
