Don’t cache the user session. Else you might work with your cache and your user itself may be not even signed in. But the cache is still valid. And that just one of many problem that you can have with cache. So don’t cache it.

Choose one these methods for auth:
jwt: json object that is signed by the server. It can’t be changed. No more database calls needed to retrieve data. The whole object will be saved in client

Session: you only save a session token clientside and you need to make an extra call to your database to retrieve the data of the session.

I prefer jwt. What about you?

I’m using both (At least I think so)

In my callbacks I’ve jwt and session

do you only get an id or do you get a full object?

But I wanted to save as a session, because when I log on to my Dashboard, the session items don't set and therefore the items related to the session (such as the user's role) aren't displayed directly.)

Full object

(Sorry I’m at school and didnt have discord on computer 😂)

can you scroll a little bit to the top. There should be a "strategie"

you are using "jwt" as method. So your "session" contains all the fields, that you added and is saved on the client. So you don't need additional database calls and your "session" is cached clientside

So be able to access your additional values form your session (typescript), you can add a next-auth.d.ts under types/... inside your root folder. Add the following to it:

import {DefaultSession} from "next-auth"

declare module "next-auth/jwt" {
    /** Returned by the `jwt` callback and `getToken`, when using JWT sessions */
    interface JWT {
        /** OpenID ID Token */
        idToken?: string
    }
}

declare module "next-auth" {
    /**
     * Returned by `useSession`, `getSession` and received as a prop on the `SessionProvider` React Context
     */
    interface Session {
        user: {
            id: string
            groups: string[] // here you can add your additional fields. In my case "groups"
        } & DefaultSession["user"]
    }
}

Yeah I already have this file

But im using additional calls to the database?

why?

No, but I was asking the question because I don't know if I do or not.

if you getting just the session by doing for example:

const session = await getServerSession(authOptions);

There is no additional call to the database

Yeah, that’s why am I doing in addition to useSession() client side

the useSession() result gives you the same result as this example: https://nextjs-forum.com/post/1253617728535924776#message-1253674744637558877

Sorry I haven't been in front of the computer since our conversation. Okay thanks for your help I get it now!

Sure thing. Please mark solution

Yeah sure, but can I ask you a question before ?

I'd like to make a system that would allow users to put something in favorite .

What would be the best way to do this?

I would create a join table for it. A join table of „Something“ and „User“ and if a user likes „Something“ create a entry inside this join table. You need the join table, because one user can have many „Something“ and one „Something“ can have many „User“. So a many-to-many connection. Solve it by using a join table

Okay, I see. So you'd send a request every time the user bookmarked something?

Perfect, thanks dude 👍

sure thing