Right now, if you set a cookie on your backend and try to use AuthKit with nextjs on your frontend, it will not work unless you set the cookieName to "wos-session".
This would allow users who are integrating with workOS in a full stack application to customize the cookieName used. For example, in a nodejs backend:
Fixes issue #58
Right now, if you set a cookie on your backend and try to use AuthKit with nextjs on your frontend, it will not work unless you set the cookieName to "wos-session".
This would allow users who are integrating with workOS in a full stack application to customize the cookieName used. For example, in a nodejs backend:
Then you would set the optional env var
WORKOS_COOKIE_NAME
on the frontend and AuthKit would automatically and properly consume the cookie 🍪 😄