Are the frontend auth routes from the NextJS SDK Next-specific or able to be used with any backend as long as the config is set correctly? As far as I can tell it seems like everything just uses the same stuff from the React package, with some extra stuff added for routing & SSR support But... I'm deploying on Vercel with a Next frontend but a backend api written in a different language (Python, FastAPI), and I can NOT get APIs nor signout to work correctly for some reason. Signup and signin works fine, but trying to call any backend service from the browser with an axios request throws 401. I've tried wrapping axios outside the component function and inside useEffect(..., []). Also, after calling logout, going to /auth again doesn't redirect to the signin screen unless I manually clear browser cookies. Protecting a page with the ThirdPartyEmailPasswordAuthNoSSR also doesn't redirect to signin after I've signed out, unless I manually clear the cache. The backend endpoints work fine when tested from Insomnia. I thought it might just be an issue with dev mode but I've tried fully building it too.

hey @mlegls

Right. For the backend I just followed the documentation's instructions for FastAPI for Python

yea makes sense..

Right, I took all that stuff out

cool

how do I enable debug logging?

see the troubleshooting section in the docs

oh hmmm I think I fixed the issue myself just by changing the api route from 127.0.0.1 to localhost lol

hmm! cool

I wonder why that's an issue though

well.. are you putting your API domain as 127.0.0.1?

I mean I changed it in frontendConfig. It was apiDomain: "http://127.0.0.1:8000" and I changed it to apiDomain: "http://localhost:8000"

right. So if you are querying localhost, then the apiDomain should be that.. else the interceptors won't be applied on the frontend and it won't work

oh I see

the cookies are not being sent. That;s the problem

I've gone through each of the items but still can't figure out what's wrong. I've tried running the request with fetch instead of axios from the frontend, and the browser's dev tools say the request is initiated from recipeImplementation.js, so I'm pretty sure it's being intercepted. Also, the same endpoint works perfectly fine from Insomnia. I can see that the Insomnia request includes the sAccessToken cookie though, while the browser request doesn't.

\Can you show me the response headers and request headers for the sign in API call? (a screenshot would do)

I tested some more, and it actually works fine from Chrome, but not from Safari...

I see. So the issue there is that the websiteDomain doesn’t have anything common with the apiDomain value.