Cool! Lmk if you run into any issues or see something that's weird

It works! Cool, that's smooth!

Verify session seems to not be triggering

Are you using it in your route? Like I have in the example?

Yup, identically. When I auth I see the session is set properly in my storage as well

I get a 401 when attempting to visit the URL or trying to consume it in my front-end

Right. Have you set the apiDomain And websiteDomain values correctly on the frontend and backend?

yep, identical on both

Are you using axios on the frontend? If yes, have you added the supertokens interceptor to it for all axios imports?

Yes & yes

Hmmm

Let’s get on a call to debug this? I know the lob works fine and that the example app also works fine. Probably some config error..

We can have the call sometime on Monday?

@Infatuation did you get the code to work?

@User I did not

I might be able to do a call monday but I work throughout most of the day.

@User I can do a call now also if you'd like.

That'd be amazing. Give me 10 minutes or so I'm just finishing up breakfast

Alright.

Good to go!

@User just to recap the issue and the solution: You were using https://localhost as your API domain and that caused an issue of incorrectly setting cookie config, which prevented the browser to store the cookies. This was solved by adding samesite=none and secure flag to the generated cookies.

Thank you so much for your help!

We will probably release a fix for the localhost issue when used with https, so that you can remove those two configs (the SDK should have figured those out on its own)

here is an issue for it for you to follow: https://github.com/supertokens/supertokens-golang/issues/36

the verifySession function is there a way I can call this as a normal function to get the session object back and not as a middleware? I am using tsoa atm and they don't have great support for express middleware atm. They only expose the req object

try {
const session = await verifySession(req, {}, () => {})
}

or can I wrap it in a promise and pass resolve as the next

Yes. There is - a function called getSession: https://supertokens.io/docs/session/common-customizations/sessions/session-verification-in-api/get-session

it will work with a empty object for the res?