Replies: 1 comment 1 reply
-
From the docs you link to, make sure you read this
your custom backend should create its own tokens. NextAuth.js tokens are only meant for the app itself. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently trying to share secure session tokens across subdomains, and for NextAuth I'm using the database strategy (so no JWTs).
As of right now, I've set the options for my session token cookie to something similar to this example in the documentation except I have
secure: false
. This works when I try to send the session token from my frontend to an api on a subdomain (e.g. fromexample.com
toapi.example.com
). However, when I set thesecure
option tofalse
, it somehow is no longer included in the request. Does anyone know why this is the case?Additionally, is it even possible to decrypt the secure session token cookie that is sent along with a request?
Beta Was this translation helpful? Give feedback.
All reactions