I'm using Next.js (frontend and SSR) + FastAPI (as...
# support-questions-legacyp
petrgazarov
04/23/2023, 8:40 AMI'm using Next.js (frontend and SSR) + FastAPI (as a traditional backend). The FastAPI backend is the same application logically (same domain and can be called from the browser directly). Do you recommend using a JWT session for this architecture, and sending the JWT to FastAPI?
r
rp_st
04/23/2023, 8:41 AMHey @petrgazarov I wouldn’t recommend enabling the JWT feature here. Just use the session cookies and use our backend SDK to verify the sessions in fastapi
p
petrgazarov
04/23/2023, 8:50 AMI see, makes sense! I'm also considering having multiple domains.
Like so:
app.my-domain.com (client application)
api.my-domain.com (api)
In this case, I can't set a cookie for api because it's not the same domain. Is there a way to make a non-JWT approach work in this case?
c
channels
04/23/2023, 9:06 AMhey i apologise if i am wrong, but i think looking into cors will clear this up
r
rp_st
04/23/2023, 11:40 AMAlso, there is a setting called cookieDomain in the backend’s session.init which allows you to share cookies across sub domains.
rp_st
04/23/2023, 11:41 AMSetting the value to “.my-domain.com” would allow sharing across all the sub domains of that site
p
petrgazarov
04/23/2023, 10:43 PMCool thanks
petrgazarov
04/24/2023, 6:34 AMI haven't tried it in production on different domains yet, but so far it works nicely on localhost. I use Next.js for session verification only, all other supertokens backend routes are in FastAPI.
petrgazarov
04/24/2023, 6:36 AMLove that supertokens is very flexible. It definitely has a learning curve, but the more I use it, the more I like it.
r
rp_st
04/24/2023, 6:39 AMgreat! let us know if you run into issues 🙂
73 Views