Discuss NextAuth.js v5 #8487
Replies: 92 comments 200 replies
-
|
@balazsorban44 I got the latest version and i want to provide multi-authentication in my app(manuel one and Google provider). In middleware i use |
Beta Was this translation helpful? Give feedback.
-
|
Haven't encountered that. Sorry, no idea how to solve that one :-/ |
Beta Was this translation helpful? Give feedback.
-
"overrides": {
"@auth/core": "0.13.0"
}should not be needed anymore either |
Beta Was this translation helpful? Give feedback.
-
|
I have this issue with the latest version |
Beta Was this translation helpful? Give feedback.
-
|
@yekdagets did you end up fixing this? Am in the same situation now : client component that runs |
Beta Was this translation helpful? Give feedback.
-
|
auth works server side, so if you want to use auth in client component you can declare a function on another file with 'use server' at the top something like this 'use server' export async function getSession() { and you can import getSession in a client component, hope this help you |
Beta Was this translation helpful? Give feedback.
-
|
@balazsorban44 is OAuth va OIDC supported on the edge runtime with v5? I've only seen credential provider and email-http provider mentioned so far. I've hit the following error when using It looks like this has been raised before (1 2), but issues were closed without fixes. It seems logical as Have I misconfigured something or is this a known issue? Versions
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@samtgarson did u figure out with Google provider and middleware together? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @balazsorban44, I knew it must be something like this. I’ll give it a try this evening and let you know @yekdagets 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
@samtgarson if u handle it, can you share with us? |
Beta Was this translation helpful? Give feedback.
-
|
Cleaning up my versions as described in that linked reply worked (at least, I’ve moved forward to a different error…) |
Beta Was this translation helpful? Give feedback.
-
|
Just came across something - maybe - missing?! When we try to use the ExamplePath: Gives me this TS error: Did I miss something about this in the PR discussion? |
Beta Was this translation helpful? Give feedback.
-
|
I am also getting the same issue as well, when working with my app, it does work, not sure if it's just TypeScript that is complaining. |
Beta Was this translation helpful? Give feedback.
-
|
@Dimitry-prog Can you please share a example config? I'm facing the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
Solution -- Just end the control with a simple return. |
Beta Was this translation helpful? Give feedback.
-
|
I found out if you combine the middleware with auth.config, it will solve the overload match issue, but I had other issues with callbacks, the best solution is to return if clauses by NextResponse.next(); which works perfectly. |
Beta Was this translation helpful? Give feedback.
-
|
i have same issue. how can we solve that? any example code? @balazsorban44 |
Beta Was this translation helpful? Give feedback.
-
|
What's the latest story with supporting lower level HTTP client options? There was a pretty length discussion #3944 about struggles folks have been running into with corporate proxies. It seemed to boil down to people having to maintain their own fork or patch the library to pass custom HTTP agents. Luckily my use case #8491 only requires a simple pass through of a https://authjs.dev/guides/corporate-proxies/corporate-proxy and the v5 migration guide should probably be updated at the very least. |
Beta Was this translation helpful? Give feedback.
-
|
Hi ! I face the same error as above : my package.json: I try the override method but it doen't seem to work for me. |
Beta Was this translation helpful? Give feedback.
-
|
You do not need the @auth/core as dependency. Just as override. That is a safe fix for the "raw" issue. How did you setup the override? And what package manager do you use? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you I didn't know for I'm using pnpm. Setup: "pnpm": {
"overrides": {
"@auth/core": "0.13.0"
}
}
Seems to be working now. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
should not be needed anymore either. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I'm quite new to Nextjs and with next-auth. I'm currently rewrite an app with Nextjs App router & i'm using Next-Auth v5. You always need to be authenticated to use the app. I'm facing two main issue with Next-auth at the moment : 1. Redirect to provider login screen instead of next-auth when user is not logged in Currently i created a 2. Logout should also log out from the provider For signout i use server actions : import { CSRF_experimental } from '@/auth'
export function SignOut(props: any) {
return (
<form action='/api/auth/signout' method='post'>
<button {...props} />
<CSRF_experimental />
</form>
)
}I think to use the |
Beta Was this translation helpful? Give feedback.
-
|
Been using NextAuth v5 for a while now and overall I'm super happy. However, I have one major issue with this new update, especially regarding the decision not to run the session callback. What is the recommended way to retrieve more user info in v5 now that the session callback isn't invoked on the server? Before it was trivial to return extra user / session fields from the adapter and have access to that in the session callback, but now it doesn't seem like that's the case. It doesn't matter what my adapter returns, since you cut half of it away anyways... I don't understand this decision since it seems to just make it harder to modify the default behaviors... Example usecase, I put an Can you shed some light on how to achieve this with this new update? Right now I'm patching next-auth to invoke this callback with all info, as the calls are on the server I don't have to care about leaking this to the client anyways... Auth core patch: diff --git a/lib/routes/session.js b/lib/routes/session.js
index e496d921578b735e640d1fc766582831dcbfdb1c..3ce6dcae1c2544fa4f439b551b5cecf3f561ad17 100644
--- a/lib/routes/session.js
+++ b/lib/routes/session.js
@@ -89,9 +89,8 @@ export async function session(params) {
// Pass Session through to the session callback
// @ts-expect-error
const sessionPayload = await callbacks.session({
- // By default, only exposes a limited subset of information to the client
- // as needed for presentation purposes (e.g. "you are logged in as...").
session: {
+ ...session,
user: { name: user.name, email: user.email, image: user.image },
expires: session.expires.toISOString(),
},NextAuth patch: diff --git a/lib/index.js b/lib/index.js
index 5a75f390e1ed59db192587176cf6fabd229cdf84..d123a9aea1b4d861ae78a23951e1feecf831c57c 100644
--- a/lib/index.js
+++ b/lib/index.js
@@ -9,17 +9,7 @@ async function getSession(headers, config) {
headers: { cookie: headers.get("cookie") ?? "" },
});
config.useSecureCookies ?? (config.useSecureCookies = origin.protocol === "https:");
- return Auth(request, {
- ...config,
- callbacks: {
- ...config.callbacks,
- // Since we are server-side, we don't need to filter out the session data
- // See https://nextjs.authjs.dev/v5#authenticating-server-side
- session({ session, user, token }) {
- return { ...session, user: user ?? token };
- },
- },
- });
+ return Auth(request, config);
}
function isReqWrapper(arg) {
return typeof arg === "function"; |
Beta Was this translation helpful? Give feedback.
-
|
Or simply add your custom fields as columns to the User table if you use a DB Adapter. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I know, you can't include data from other models for the session, such as a (I updated my example to include a |
Beta Was this translation helpful? Give feedback.
-
Still dont understand why we cant do the same with sessions...
But maybe i dont want to expose all fields? |
Beta Was this translation helpful? Give feedback.
-
|
FWIW I totally agree -- I'd love to continue using sessions instead of JWT, but the solution I shared was the only thing that worked for me for the time being. @balazsorban44 If you could provide any insight on the decision here, or if there is another way to achieve this with sessions, it would be much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
This raised my eyebrow for me while reading the v5 docs. Hopefully we can get the reasoning behind this direction. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @balazsorban44, thanks for the v5! I ran into an issue when deploying it to Cloud Run (basically behind a proxy). The request origin is resolved to Now, I believe the issue isn't specific for v5. But it seems that there are options to bypass this in v4. Since v5 only exports the handlers and I haven't found a way to build a modified NextRequest myself, there probably isn't a workaround. What would you suggest as a fix? Should I create an issue/PR for v4? I'm happy to contribute, but would need some hints :) Edit: The patch below isn't needed. See the thread for a nicer fix! Here's a hacky patch that I'm currently applying and fixes the issue |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't something like this work? // api/[...nextauth]/route.ts
import { handlers } from "~/auth"
export const GET = (req: NextRequest) => {
// do stuff
const url = ...
return handlers.GET({...req, url });
}
// ... |
Beta Was this translation helpful? Give feedback.
-
|
Julius' suggestion is the correct way/equivalent of advanced init in a Route Handler. 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I tried that earlier, but it doesn't work. That's why I wrote that I cannot construct/modify the request by hand 😞 Maybe I'm missing something. But That leads to various errors in NextAuth internals, such as
And the same is also signalled by TS |
Beta Was this translation helpful? Give feedback.
-
|
What if you make a new object with your modified URL? export const GET = (req: NextRequest) => {
const url = new URL(req.url);
url.pathname = url.pathname.replace("/api/auth", "");
return getHandler(new NextRequest(url, req));
}; |
Beta Was this translation helpful? Give feedback.
-
|
@juliusmarminge yes, that worked! Thank you 🙌 If anyone finds this thread, here's my full import {GET as authGET, POST as authPOST} from '@/auth'
import {NextRequest} from 'next/server'
export const GET = (req: NextRequest) => {
const patchedUrl = patchUrl(req.url)
return authGET(new NextRequest(patchedUrl, req))
}
export const POST = (req: NextRequest) => {
const patchedUrl = patchUrl(req.url)
return authPOST(new NextRequest(patchedUrl, req))
}
/**
* Next doesn't properly handle requests when behind a proxy (e.g. Cloud Run).
* There's an existing env var, but it's not used in all places.
*
* Here, we patch the url to use the NEXTAUTH_URL env var and leave the rest of the request intact.
* Hopefully it doesn't break anything, but it's only used for the auth routes.
*/
function patchUrl(url: string) {
const urlObj = new URL(url)
const origin = process.env.NEXTAUTH_URL ?? urlObj.origin
return url.replace(urlObj.origin, origin)
} |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
In Server Components use |
Beta Was this translation helpful? Give feedback.
-
|
Did something change in the type-definition for the I'm looking to implement the HTTP-based Email provider following this doc but TypeScript is very unhappy that I do not provide the It also requires that It's not a huge deal as I can always do the following: {
id: "email",
type: "email",
name: "Email",
from: "",
server: "",
maxAge: 60 * 10,
options: {},
async sendVerificationRequest(...) { ... },
}But it feels kinda dirty 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Related #8601 |
Beta Was this translation helpful? Give feedback.
-
|
@Punie do you happen to have a working example of the email provider that you can share? I keep getting |
Beta Was this translation helpful? Give feedback.
-
|
In my case i had to do it like this Also there is no way to change the id to 'mailgun' or whatever, is enforced to be 'id' so you can't have 2 email providers |
Beta Was this translation helpful? Give feedback.
-
|
@balazsorban44 since solving the previous issue I've encountered another critical issue, possibly due to my set up but I cannot fathom what I'm doing wrong: Right now, the OAuth handshake is succeeding and the session is being passed to the frontend correctly ( The What's more, the I have done everything I can to ensure the versions of my packages are correct, including clearing my lock file. I currently only have |
Beta Was this translation helpful? Give feedback.
-
|
Likely same as #7423 (comment)
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
RSC: log: |
Beta Was this translation helpful? Give feedback.
-
|
Any progress on that? Auth() returning null for me as well with Auth0Provider |
Beta Was this translation helpful? Give feedback.
-
|
work with @auth/prisma-adapter, the auth object received in the authorized callback (or inside the middleware - req.auth) is always null |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone been able to successfully use v5 with a |
Beta Was this translation helpful? Give feedback.
-
|
Did you find a solution to this? I'm also seeing this error :( |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried deleting the |
Beta Was this translation helpful? Give feedback.
-
|
Can't find a solution for this even though they say it is supported. I guess they've just written the docs before solving it. Kind of annoying tbh. Perhaps time to re-write to app folder.. |
Beta Was this translation helpful? Give feedback.
-
|
Deleting and Re-Installing |
Beta Was this translation helpful? Give feedback.
-
|
same issue on my side |
Beta Was this translation helpful? Give feedback.
-
|
@balazsorban44 It seems that once cannot import anything into middleware that has |
Beta Was this translation helpful? Give feedback.
-
|
Ignore ORMs, what about the auth configs... that is super sensitive stuff that you would want to put |
Beta Was this translation helpful? Give feedback.
-
|
What's sensitive? Your envs wont be accesible to client with or without server-only |
Beta Was this translation helpful? Give feedback.
-
|
True... but that means anything you include in middleware cannot be included on your server. And there are things that are sensitive. |
Beta Was this translation helpful? Give feedback.
-
As soon as this file gets marked as This is not exclusive to Auth, really anything that you need a middleware for, can't be marked as |
Beta Was this translation helpful? Give feedback.
-
|
@barryengineerapart for what it's worth, I am also concerned, not only because of this but also because the notion of importing the same At first I wasn't sure what to think about this API, but after using it, while I get the convenience of only having one |
Beta Was this translation helpful? Give feedback.
-
|
Code Error Code Error |
Beta Was this translation helpful? Give feedback.
-
|
Route handlers in the app directory have a slightly different implementation to API routes in the pages directory. Go checkout the next docs for Route Handlers, they have some clear examples. (This isn’t anything to do with NextAuth though |
Beta Was this translation helpful? Give feedback.
-
Hi, I have already tried to implement these solutions, but the error still seems to appear. |
Beta Was this translation helpful? Give feedback.
-
export async function GET(req: NextRequest) {
// Check if user is logged in
const session = await auth(); // shouldn't need to pass req to auth functions, headers are globally available
if (!session || !session.user) {
console.log("User not logged in");
return NextResponse.json("You must be logged in to upload.", { status: 401 });
}
// Query the database by email to get the number of generations left
const user = await prisma.user.findUnique({
where: {
email: session.user.email!,
},
select: {
credits: true,
location: true,
},
});
return NextResponse.json({
remainingGenerations: user?.credits
});
} |
Beta Was this translation helpful? Give feedback.
-
|
In order to implement a custom signin page, what is the new method to get the provider list? Before it was |
Beta Was this translation helpful? Give feedback.
-
|
You can fetch /api/auth/providers ? |
Beta Was this translation helpful? Give feedback.
-
|
no, that does not work |
Beta Was this translation helpful? Give feedback.
-
|
@TSV-KG It does work, but we need type definitions, I'm looking to make PR for that. |
Beta Was this translation helpful? Give feedback.
-
|
if it does not work, check your sessionprovider implementation |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, I'm currently working on a Next.js project where we've integrated Setup Overview
Encountered IssueDuring integration tests, specifically when testing tRPC procedures that utilize Error: Cannot find module '/path/to/project/node_modules/next/server' imported from /path/to/project/node_modules/next-auth/lib/env.js vbnet This error surfaces when executing a test that involves creating a tRPC context with a mocked session, specifically through the use of Test ExampleHere's a simplified version of the test that triggers the error: import { createInnerTRPCContext } from "./../server/api/trpc";
test("hello test", async () => {
const ctx = createInnerTRPCContext({
session: {
user: { id: "123", name: "John Doe" },
expires: "1",
},
});
// Further logic to call a tRPC procedure
});And the related createInnerTRPCContext function involved: import { auth } from "@/app/api/auth/[...nextauth]/auth";
export const createTRPCContext = async (opts: { headers: Headers }) => {
const session = await auth();
return createInnerTRPCContext({ session });
};Has anyone experienced a similar issue or could provide insights into how to navigate this problem? Thank you in advance for your help and insights! |
Beta Was this translation helpful? Give feedback.
-
|
Im facing the same issue when I try to run auth(). I created a function in my libs folder with use server at top to return the value of the auth() function and its returning the same error. |
Beta Was this translation helpful? Give feedback.
-
|
Did you guys figure this out? When i try to run Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Adding this code to vitest.config fixed the issue for us, no idea why: export default defineConfig({
test: {
environment: "node",
server: {
deps: {
inline: ["next-auth"],
},
},
},
}); |
Beta Was this translation helpful? Give feedback.
-
|
Im currently working on updating the Eveonline Provider. While this is great supporting more JWT , Im currently trying to figure out how to use the JWT token. As i try to remove this line in the code I'm wondering if anyone would know the proper way to accomplish the Auth flow while removing the userInfo ? |
Beta Was this translation helpful? Give feedback.
-
|
I'm having an issue with an |
Beta Was this translation helpful? Give feedback.
-
|
Would anyone here happen to know if the optional |
Beta Was this translation helpful? Give feedback.
-
|
Not yet, but it's pretty much the same as v4, https://authjs.dev/reference/nextjs#authorized. |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thanks so much. |
Beta Was this translation helpful? Give feedback.
-
|
I am running a Nextjs (v14.1.4) app with NextAuth (5.0.0-beta.16), Google OAuth, JWT strategy and persisting to MongoDB using an adapter pattern. Everything works great in development but in production I cannot complete a call to signIn without the serverless function timing out. I even configured the regions to use the same as my MongoDb cluster. |
Beta Was this translation helpful? Give feedback.
-
|
Alright let me give a complete code example of what I have. package.json "dependencies": {
"@amplitude/analytics-browser": "^2.3.3",
"@auth/mongodb-adapter": "^2.5.2",
"@sentry/nextjs": "^7.109.0",
"bcryptjs": "^2.4.3",
"cookie": "^0.6.0",
"jsonwebtoken": "^9.0.2",
"mongodb": "^6.5.0",
"mongoose": "^8.2.2",
"next": "^14.1.4",
"next-auth": "^5.0.0-beta.16",
"nextra": "^2.13.3",
"nextra-theme-docs": "^2.13.3",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-icons": "^5.0.1",
"sharp": "^0.33.3",
"unique-username-generator": "^1.3.0"
},src/app/api/auth/[...nextauth]/route.ts // cannot run this on the edge, it requires mongoDB
// export const runtime = 'edge';
export { GET, POST } from "@/src/auth";src/auth.ts import NextAuth from "next-auth";
import { MongoDBAdapter } from "@auth/mongodb-adapter"
import { authConfig } from '@/src/auth.config';
import { mongoClientPromise } from "@/src/utils/mongodb";
export const {
auth,
handlers: { GET, POST },
signIn,
signOut,
} = NextAuth({
...authConfig,
adapter: MongoDBAdapter(mongoClientPromise, {
databaseName: process.env.ENVIRONMENT,
}),
session: {
strategy: 'jwt', // force JWT session with a database
},
});src/auth.config.ts import type { NextAuthConfig } from 'next-auth';
import GoogleProvider from "next-auth/providers/google";
import {
ProtectedRoutes,
RbacUsers,
userHasAccess
} from '@/src/constants';
import { generateRandomUsername } from '@/src/utils/randomUtils';
export const authConfig = {
providers: [
GoogleProvider({
clientId: process.env.GOOGLE_CLIENT_ID!,
clientSecret: process.env.GOOGLE_CLIENT_SECRET!,
profile(profile) {
// console.log('profile: ', profile);
return {
// Return all the profile information you need.
// The only truly required field is `id`
// to be able identify the account when added to a database
id: profile.sub,
name: profile.name,
email: profile.email,
image: profile.picture,
// Add a new one
isAdmin: RbacUsers[profile.email].isAdmin,
username: generateRandomUsername(),
// role: // logic for role...
}
},
}),
],
// callbacks go in this file according to next:
// https://nextjs.org/learn/dashboard-app/adding-authentication
// callbacks cycle: authorize --> jwt --> session
callbacks: {
async authorized({ request, auth }) {
// Get the pathname of the request (e.g. /, /protected)
const path = request.nextUrl.pathname;
const token = auth?.id_token;
const isProtected = Object.values(ProtectedRoutes).some(route => path.includes(route));
// Just render the root path
if (path === '/') return true;
// if the route is protected and they are not signed in, redirect them home.
if (isProtected && !token) {
return Response.redirect(new URL('/', request.nextUrl));
}
if (token && isProtected) {
if (userHasAccess({ userEmail: auth.user?.email, route: path })) return true;
// if the user does not have access send them to the home page
else return Response.redirect(new URL('/', request.nextUrl));
}
},
// Use the signIn() callback to control if a user is allowed to sign in.
async signIn({ user, account, profile }) {
// console.log('signIn - user: ', user);
// console.log('signIn - account: ', account);
// console.log('signIn - profile: ', profile);
// Google also returns a email_verified boolean property in the OAuth profile.
// Using this property to restrict access to people with verified accounts at a particular domain...
if (account && account.provider === "google") {
return true;
}
return false;
},
// The session callback is called whenever a session is checked.
async session({ session, token, user }) {
// Send properties to the client, like an access_token from a provider.
session.accessToken = token.accessToken as string;
session.id_token = token.id_token as string;
session.user.id = token.id as string;
session.user.isAdmin = token.isAdmin as boolean;
session.user.username = token.username as string;
// for role based auth...
// https://authjs.dev/guides/basics/role-based-access-control
// session.user.role = token.role
// console.log('session - session: ', session);
// console.log('session - token: ', token);
// console.log('session - user: ', user);
return session;
},
// This callback is called whenever a JSON Web Token is created (i.e. at sign in) or updated (i.e whenever a session is accessed in the client). The returned value will be encrypted, and it is stored in a cookie.
// The arguments user, account, profile and isNewUser are only passed the first time this callback is called on a new session, after the user signs in. In subsequent calls, only token will be available.
async jwt({ token, user, account, profile }) {
// Persist the OAuth access_token to the token right after signin
if (account && account.access_token) {
token.accessToken = account.access_token;
token.id_token = account.id_token;
}
// for role based auth....
// if (user) token.role = user.role
// console.log('jwt - token: ', token);
// console.log('jwt - account: ', account);
// console.log('jwt - user: ', user);
// console.log('jwt - profile: ', profile);
return { ...token, ...user };
}
},
pages: {
signIn: "/auth",
signOut: "/auth",
},
secret: process.env.NEXTAUTH_SECRET!,
} satisfies NextAuthConfig;src/middleware.ts import NextAuth from 'next-auth';
import { NextRequest, NextResponse } from 'next/server';
import { authConfig } from './auth.config';
const { auth } = NextAuth(authConfig);
export default auth((req) => {
const path = req.nextUrl.pathname;
// console.log('path: ', path);
return NextResponse.next();
});
// Optionally, don't invoke Middleware on some paths
export const config = {
matcher: ["/((?!api|_next/static|_next/image|favicon.ico).*)"],
}mongodb.ts // This approach is taken from https://github.com/vercel/next.js/tree/canary/examples/with-mongodb
import { MongoClient } from "mongodb";
import { Environments } from "@/src/constants";
if (!process.env.MONGO_URI) {
throw new Error('Invalid/Missing environment variable: "MONGO_URI"');
}
const uri = process.env.MONGO_URI;
const options = {};
let client;
let mongoClientPromise: Promise<MongoClient>;
if (process.env.NODE_ENV === Environments.development) {
// In development mode, use a global variable so that the value
// is preserved across module reloads caused by HMR (Hot Module Replacement).
if (!global._mongoClientPromise) {
client = new MongoClient(uri, options);
global._mongoClientPromise = client.connect();
}
mongoClientPromise = global._mongoClientPromise;
} else {
// In production mode, it's best to not use a global variable.
client = new MongoClient(uri, options);
mongoClientPromise = client.connect();
}
// Export a module-scoped MongoClient promise. By doing this in a
// separate module, the client can be shared across functions.
export { mongoClientPromise };src/types/mongodb.ts import { MongoClient } from "mongodb";
/* eslint-disable no-var */
declare global {
var mongoClientPromise: Promise<MongoClient>;
var _mongoClientPromise: Promise<MongoClient>;
}src/types/next-auth.d.ts import NextAuth from "next-auth";
import { type DefaultSession, type DefaultProfile } from 'next-auth';
declare module "next-auth" {
/**
* Returned by `useSession`, `getSession` and received as a prop on the `SessionProvider` React Context
*/
interface Session extends DefaultSession {
user: {
id: string;
name: string;
email: string;
image: string;
isAdmin: boolean;
username?: string;
}
accessToken?: string;
id_token?: string;
}
} |
Beta Was this translation helpful? Give feedback.
-
|
Everything seems normal to me. Have you happened to call the sign-in on edge runtime? Because some database drivers don't work with edge runtime. Even if it does, you need to make sure your DB connection closes at the end of the edge runtime request, else you will likely get a timeout on the subsequence request. |
Beta Was this translation helpful? Give feedback.
-
|
No it will not run even locally if the edge is enabled... |
Beta Was this translation helpful? Give feedback.
-
|
I would also just mention that I configured my app to use the Stockholm region and my mongoDB to use Stockholm as well but it still times out. I feel like you should be able to do this even on a hobby plan |
Beta Was this translation helpful? Give feedback.
-
|
@chungweileong94 you mentioned "Even if it does, you need to make sure your DB connection closes at the end of the edge runtime request, else you will likely get a timeout on the subsequence request." Maybe this explains why it works in development and not production but there is no documentation around how to ensure the connection is closed using the adapter. Do you know? I am using the recommended implementation here: https://authjs.dev/getting-started/adapters/mongodb |
Beta Was this translation helpful? Give feedback.
-
|
I noticed the "old" atlassian provider has been removed, was this move intentional? as many applications i build are dependent on it i cant move to the v5 yet. i also filed a new provider request here #10604 |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I'm having a problem with signIn with IdentityServer4 provider (tried to use Auth0 also, but the result its the same). The are my environment versions: When I click the button that runs signIn('MY_PROVIDER_ID'), its returning this error locally in my server: And this one in my page: Here's my Auth.ts code: ` export const config = { }, export const { handlers, auth, signIn, signOut } = NextAuth(config); What I tried:
Still |
Beta Was this translation helpful? Give feedback.
-
|
Can anyone help with getting the user first and last name from facebook provider, for v5? I used this in the past: Providers.Facebook({
clientId: process.env.FACEBOOK_CLIENT_ID,
clientSecret: process.env.FACEBOOK_CLIENT_SECRET,
profileUrl:
"https://graph.facebook.com/me?fields=id,name,email,picture,first_name,last_name"
profile: (_profile) => {
return {
id: _profile.id,
firstName: _profile.first_name,
lastName: _profile.last_name,
email: _profile.email,
image: _profile.picture.data.url,
};
},
}),But the profileUrl seems not available anymore. |
Beta Was this translation helpful? Give feedback.
-
|
I am experiencing issues with the Drizzle Adapter when using "In your seed.js file, you utilized a package called bcrypt to hash the user's password before storing it in the database. You will need to use it again later in this chapter to verify that the password entered by the user matches the one in the database. However, you will need to create a separate file for the bcrypt package. This is because bcrypt relies on Node.js APIs that are not available in Next.js Middleware." However, the guide does not proceed to separate Considering that many Next.js users also leverage edge functions, and Drizzle is currently a rising and popular alternative, coupled with the fact that most people require credentials authentication, I find it surprising that these functionalities are not working as expected. I spent a significant amount of time today unsuccessfully attempting to fix and investigate this issue. However, authentication implementation in 2024 should not consume this much time, especially considering that the purpose of the library, similar to Next.js, is to enhance developer experience (DX). |
Beta Was this translation helpful? Give feedback.
-
|
If I don't get an answer here I will reproduce the problem and open an issue, but again I don't feel like using Drizzle + next-auth v5 + Neon on edge deployed to Cloudflare/Vercel should take this much effort. They are all pretty new and popular technologies (ChatGPT uses most of them). Not to mention I had also problems related to this: vercel/next.js#50177 something about drizzle with postgres, but I decided to skip that problem and just switch from Supabase to Neon. |
Beta Was this translation helpful? Give feedback.
-
|
what postgress client do you use? most of them are not combatible with edge. i tried pg and postgress, both didnot work, so i switched to vercel postgress with theirs db, it is fully edge compatible |
Beta Was this translation helpful? Give feedback.
-
|
Hi folks, someone experimented an issue with next.js 14.1.4 and Keycloak? and this redirect error from Keycloak: KeycloakProvider({
id: 'keycloak',
clientId: process.env.KC_CLIENT_ID,
clientSecret: process.env.AUTH_SECRET,
issuer: process.env.KC_ISSUER_URL,
client: {
token_endpoint_auth_method: 'none',
}}) |
Beta Was this translation helpful? Give feedback.
-
|
Added a bug report (that was autoclosed, thanks to the rigid config) and pull request for the tiktok bug. See here: #10727 and #10728 |
Beta Was this translation helpful? Give feedback.
-
|
how can i pass the request to the auth function in nextauth v5 when i try to use the auth() in the pages /api directory it gives me this error |
Beta Was this translation helpful? Give feedback.
-
|
Never tested it on the page router myself, but I think we should pass in the |
Beta Was this translation helpful? Give feedback.
-
|
I'm a bit confused this apparently hasn't been discussed anywhere. The new |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use the Would it make sense to make another instance of |
Beta Was this translation helpful? Give feedback.
-
|
here is the guide for edge compatiblity, they recommend splitting config for middleware and for server https://authjs.dev/getting-started/migrating-to-v5#edge-compatibility |
Beta Was this translation helpful? Give feedback.
-
|
This has been fixed by Vercel for quite some time now.
|
Beta Was this translation helpful? Give feedback.
-
|
I assume you were replying to me, but what do you mean that it was fixed and how? |
Beta Was this translation helpful? Give feedback.
and others
-
Let's discuss #7443 here.
Keep the PR comments to discuss actual issues/concerns about the ongoing implementation. You can ask for help specific to your project here, or if you are not sure why something isn't working.
Beta Was this translation helpful? Give feedback.
All reactions