No, the UUID of the user to be shown

IE /users/:userID will show the users profile

(other user)

I see

So ur getting a try refresh token error when u give the incorrect URL

that may be because insomnia is not sending the cookies in case the URL is invalid?

U should print the request headers in the Middleware (before calling getSession) and see what insomnia sends

Ok

Yeap you're right! sorry

👍

Hey @User , I keep making the mistake of forgetting to turn on supertokens via

supertokens start dev

on powering up machine and anytime after I run

supertokens stop dev

and it takes me a little while to remember. Is there any way to make it so that my app throws an error (possibly at init([])) for supertokens, incase I forget?

Hi @User . Apologies for the late reply. We have purposely made the init function not throw an error since this way, your node app can start regardless of ST working at that time or not. Otherwise in a production environment when processes are starting simultaneously, there will be a race condition between your node process and ST. One way to fix this issue of yours is to automatcally start ST on mac bootup. Or else using a docker container with restart mode on.

Finally, we also thought that if you are running ST in dev mode, to somehow throw that error when u call the init function in node. However, that is not possible either since the node process doesn't know what mode you are running ST on before a handshake. And for a handshake to be successful, you already have to be running ST. One more thing we thought of is that the node process starts the ST process in case it's not running - however, that is a break in the isolation principle which us "unclean" and will most certainly cause issues in the future. We will try and think of more ways to solve this issue as to make your experience more smooth. Will let u know! Thanks for the feedback

All of those seem like very valid reasons to not do this! Thanks for the info

👍

Hey RP if one wanted to use Swagger for documentation of the API that uses supertokens, would the browser automatically know how to deal with the cookies or is there something I have to do?

@User I don't think so. I'm not too familiar with Swagger. What exactly do you want to do though? Maybe I can suggest alternative methods that I am familiar with.

Ah, that's a shame was going to use swagger to document all of my endpoints as I already have joi validation on each and therefore I'd get all of the documentation for free. It would look like this for me:

I mean, it could be possible. But I do not know

I think it actually is possible just needs some setup

Hi, I am trying to integrate SuperTokens into my VueJS app. in the main.js file I am importing and using the init function, but, I keep getting this error. index.js?1e2f:249 Uncaught TypeError: Cannot read property 'startsWith' of undefined at getDomainFromUrl (index.js?1e2f:249) at Function.AuthHttpRequest.init (index.js?1e2f:309) at Function.AuthHttpRequest.init (axios.js?792a:296) at eval (SignInForm.vue?79c6:41) at Module../node_modules/cache-loader/dist/cjs.js?!./node_modules/babel-loader/lib/index.js!./node_modules/cache-loader/dist/cjs.js?!./node_modules/vue-loader/lib/index.js?!./src/components/SignInForm.vue?vue&type=script&lang=js& (app.js:1324) at __webpack_require__ (app.js:790) at fn (app.js:101) at eval (SignInForm.vue?ee37:1) at Module../src/components/SignInForm.vue?vue&type=script&lang=js& (app.js:5478) at __webpack_require__ (app.js:790)

I was wondering if you could help out as to why this would be happening?

Nevermind, it was user error, instead of using requestTokenUrl instead of refreshTokenUrl, sorry. 🤦‍♂️

Ah ok! I hope you got it to work finally

Hi. So I was able to get it working to the point of signing in with supertokens. Now that I am signed in, when I run doesSessionExist() it says false, which should not be true. I am unaware what to do to refresh a token, or check if the token is still valid, the documentation does not really give any instructions. Any help would be appreciated

I had a quick question For front end integration, am I correct to assume calling SuperTokensRequest.makeSuper(axios) adds interceptors that handle token expiry automatically?

Hey @SynKnuckle after calling the create new session function, check cookies on ur frontend. Does it contain a cookie called IRTFrontend?

@tredstone that’s correct!

Wait! It handles token expiry automatically? I don't understand. Does it handle the refresh?