If you are using workOS to integrate into a full stack app (a separate backend and frontend) then you have to set the cookie in the backend and consume it in the frontend.
The AuthKit package for nextjs will only consume the cookie properly if you set the cookieName in the backend to "wos-session". This is because it's hardcoded here and then consumed elsewhere as cookieName.
PaulAsjes
commented
1 week ago
Issue
If you are using workOS to integrate into a full stack app (a separate backend and frontend) then you have to set the cookie in the backend and consume it in the frontend.
The AuthKit package for nextjs will only consume the cookie properly if you set the cookieName in the backend to "wos-session". This is because it's hardcoded here and then consumed elsewhere as cookieName.