which core version are you using?

I am not sure I do... in the package JSON file the only ST-related thing I have is

"supertokens-node": "^8.0.1",

what's your connectionURI?

that must be connected to a core that we managed (an older version - when you signed up)

most likely yeah, I signed up quite some time ago... 😄

right. We can update the core version for you if you'd like.

sent you a PM.

Yes, sir! pls, do! 🙂

Until then, you can use

https://try.supertokens.io

as your connectionURI value and it should work

I'l notify you

once the update is done

yes, I prefer to wait for the real deal.

does it take very long time?

Cool.

> does it take very long time? No... it would have been done in a few mins. But since it's saturday night, I might have to wait for our backend dev to be available to upgrade it 🙂

ah, no worries. totally forgot it's Saturday haha

haha

update for my issue: the guys at ST updated the core version running for my managed instance and now everything is fine. 😺 btw @User , I am getting back two cookies -

sAccessToken

and

sIdRefreshToken

while in the docs it says I should get back

sIdRefreshToken

,

sAccessToken

and

sRefreshToken

.

Oh. Can I see the response headers please?

From the login requests

yes.

I see a header for the missing cookie but it's not actually received.

The cookie is sent as you can see. Are you using chrome for this?

nah, this is Postman.

Can you send a request to the refresh endpoint?

If that returns a 200, then postman is storing the cookie as expected.

Just maybe it’s not visible for some reason. That happens in chrome for example. To see the refresh cookie, you have to visit the exact path that it’s stored against. Only then chrome shows it

Perhaps postman does something like this too?

okay, will try in a second. the docs say

Set the URL as http://localhost:3001/auth/session/refresh

but shouldn't I call my own API instead? 🤔

Yea. You should call your own API