The NextAuth implementation in API routes seems to be causing issues as the unstable_getServerSession and getToken functions consistently

Question

The NextAuth implementation in API routes seems to be causing issues as the unstable_getServerSession and getToken functions consistently

Struggling with utilizing the unstable_getServerSession in a nextJS API route after switching from a custom authentication method. Wondering if I may have misconfigured JWT or missing something obvious.

Referenced the tutorial "Securing API routes": pages/api/get-session-example.js https://next-auth.js.org/tutorials/securing-pages-and-api-routes#securing-api-routes

Utilizing the getServerSideProps function to make an Axios call to my next/API endpoint
Sending a Bearer token in the header of the next/API call
Expecting the API endpoint to authenticate the user using JWT
Subsequently fetching Stripe subscriptions based on the stripe_customer_id embedded in the JWT

However, the session and token within the next/API endpoint always return as null

This is the snippet for my getServerSideProps function:


// Code block here...

For the next/API endpoint /api/account/subscriptions:


// Code block here...

Here's the complete [...nextauth].ts file:

Mentioned that the JWT is created by a Rails backend.


// Code block here...

Seeking assistance in resolving this issue which has been persisting for days without resolution. Cross-posting from GitHub to StackOverflow in hopes of getting insights from the community.

typescript next.js next-auth

Answer 1

Answer №1

handling jwt callback

 return Promise.resolve(token)

dealing with session callback

return Promise.resolve(session)

executing authorize function

if (res.ok && user) {
      return Promise.resolve(user)
  }

updating user in sessions callback

session.user = token.user

Answer 2

handling jwt callback

 return Promise.resolve(token)

dealing with session callback

return Promise.resolve(session)

executing authorize function

if (res.ok && user) {
      return Promise.resolve(user)
  }

updating user in sessions callback

session.user = token.user

The NextAuth implementation in API routes seems to be causing issues as the unstable_getServerSession and getToken functions consistently

Answer №1

Similar questions

mobx: invoking a class method upon data alteration

When working with Typescript, it's important to handle errors properly. One common error you might encounter is: Error:(54, 33) TS2686: 'fabric' refers to a UMD global, but the current file is a module

Unable to locate the control specified by the path: 'files -> 0 -> postId'

Can you please explain the distinction between the .ts and .tsx file extensions? They are both commonly used for TypeScript files in a React environment, but what is the specific use case for each

What is the reason for the presence of additional mandatory dependencies in the package-lock.json file?

"Seeking guidance on getting my carousel functionality up and running in Angular 8 - any

Access the plugin object from a Vue.js 2 component using typescript

Leveraging Promise in conjunction with async/await

Instead of retrieving documents, the MongoDB query is returning topology information

Angular: Implementing conditional HTTP requests within a loop

Angular - Retrieve Excel file with its current filename

Is the subdirectory set as "/blogs" using firebase?

What could be causing the lack of updates in my shared service across all components?

Error: The specified property 'Body' is not found within the type '{}'

MQTT Broker specialized in Typescript

New Image module featuring multiple SrcSet-Images

Sending data to a parent component from a popup window in Angular Material using a button click while the window is still open

Is there a more efficient method in Typescript to define the types of an object containing arrays?

Utilizing Typescript and sinon to mock the functionalities of jsonwebtoken

Encountering compilation errors during the vue-cli build process