Hello. I'm having trouble with the Session (Only) Recipe. I am able to create a boilerplate project just fine, but once I start introducing routes to my express server, I'm getting CORS errors. My config looks good (

websiteDomain

and

apiDomain

looks fine on both front-end and backend). I am trying to do a GET request from a basic, unprotected route before making a second API call to create Session on the backend. The first GET request to

http://localhost:4000/authenticate/...

fails so the second request that begins the SuperToken logic on the backend never gets called. Can anyone offer any insight here?

hey @cristoforo do you use graphql or anything else that could be overwriting the cors middleware setting?

No graphql. I don’t think anything else is overwriting. Is it ok to hit server with standard api calls unrelated to super token? I would assume yes.

it is

I am serving this from AWS API Gateway:

Oh yea. For sure. You need to set the right cors in aws gateway as well

hm. I am serving the app there on line 39 and it should be using the cors middleware with options I sent you in my previous screenshot.

Right. But the api gateway is probably overwriting the cors headers

ok i will look into this.

it should - yea