next auth limitations with server rendering?
https://github.com/KairuDeibisu/wysark
Here's the skinny,
I'm using planet scale for my back end then prisma to connect it to next JS.
I'm using auth0 for authentication and role-based management.
I'm using next auth to manage the session with the auth 0 provider.
What feels like at random, changing components unrelated to authentication, it's causing the token in the middleware to become null only in production.
While the navbar is reacting to the login as if the users logged in. This would mean, The use session hook is correctly getting a token. While the req.nextauth.token is not being set.
I'm definitely overlooking something, but after 2 weeks, I decided I need help.
Everything is working perfect on my local machine.
This was an issue before because there was some special characters in my secret key that vercell did not like. But changing it worked, until I pushed a new change to nav bar today.
Here's the skinny,
I'm using planet scale for my back end then prisma to connect it to next JS.
I'm using auth0 for authentication and role-based management.
I'm using next auth to manage the session with the auth 0 provider.
What feels like at random, changing components unrelated to authentication, it's causing the token in the middleware to become null only in production.
While the navbar is reacting to the login as if the users logged in. This would mean, The use session hook is correctly getting a token. While the req.nextauth.token is not being set.
I'm definitely overlooking something, but after 2 weeks, I decided I need help.
Everything is working perfect on my local machine.
This was an issue before because there was some special characters in my secret key that vercell did not like. But changing it worked, until I pushed a new change to nav bar today.
GitHub
Contribute to KairuDeibisu/wysark development by creating an account on GitHub.
