Do you need NextAuthOptions?

Unanswered

King Shepherd posted this in #help-forum

King ShepherdOP

2023-08-07T07:43:06.000Z

I'm seeing some people wrapping their providers/session options in a NextAuthOptions object, and using that as a param into NextAuth() and then exporting that as GET and POST in [...nextauth]/route.ts.

Apparently the justification for this, is that they can pass those NextAuthOptions to getServerSession() so that getServerSession() knows how/where to look for the session. Is this necessary? Are there simpler ways to gain what is being gained this way? or no

In the documentation i'm not seeing the use of NextAuthOptions. It just shows wrapping your options in NextAuth() and then exporting it as the handler as GET and POST.

The first picture is using NextAuthOptions in api/auth/[...nextauth]/route.ts, the second is the "getting started" documentation's api/auth/[...nextauth]/route.ts

23 Replies

fuma 💙 joulev

2023-08-07T10:20:44.000Z

If you have injected some properties into sessions, such as a user id, it will be necessary to pass authOptions into getServerSession.

King ShepherdOP

2023-08-07T22:41:20.000Z

Thanks. What would it look like in code to inject a user ID into a session?

Just defining another category in this block?

fuma 💙 joulev

2023-08-08T02:53:12.000Z

Here is an [example](https://github.com/SonMooSans/shark-chat-js/blob/main/packages/server/auth/index.ts)

Pradip Chaudhary

2023-08-10T11:08:44.000Z

callbacks: {
        session: async ({ session, token }) => {
            if (session.user != null) {
                session.user.id = token.uid;
            }
            return session;
        },
        jwt: async ({ user, token }) => {
            if (user != null) {
                token.uid = user.id;
            }
            return token;
        },
    },

Hey I had one question

when are these callbacks called and from where

& how do we get the session, token & user in these functions