You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've a little problem with my next-auth config i guess. Didn't see problem like that along the internet so I'm asking here. So my callbacks don't have access to user object generated by authorize function. Especially jwt. I got a custom backend that returns just my JWT token, so I want to store it in session object but I think I'm doing something wrong, like I don't fully understand this library. This is my [...nextauth].ts file
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I've a little problem with my next-auth config i guess. Didn't see problem like that along the internet so I'm asking here. So my callbacks don't have access to user object generated by authorize function. Especially jwt. I got a custom backend that returns just my JWT token, so I want to store it in session object but I think I'm doing something wrong, like I don't fully understand this library. This is my [...nextauth].ts file
And there in api routes session is always null
What's wrong there? I can't find any useful tutorial how to do it correctly.
Beta Was this translation helpful? Give feedback.
All reactions