Hi guys, I am the colleague of Edwin at de Lokalist, as he is on holiday, I am inheriting our production codebase with Supertokens configured. We are having an error on our Dashboard which is mostly internally used , the error being:

("Could not refresh session");

What would be the best way to debug this?

After post login is there a way to throw a error response if some conditions are not met

Noticed that the api-key specified for the super token core is getting added in to the request header at the client side, wondering if this is right behaviour since I thought that the back end node app is proxying the call to super token core.

Post login error

API key for supertokens

Is there a way to get the session handle at the client side ?

Getting session handle on the client side

hello , i am a supertoken user . i have integrated supertokens with my application. And using session context. i need to individually test react components for my unit test. but i cant seem to mock useSessionContext. could you please help me.

Good afternoon! I am new using Supertokens and have a very basic question I am working in a React + Express inventory app, and recently tested Supertoken with the EmailPassword recipe. It worked pretty well. I spinned up a MongoDB in Atlas and then I was wondering if it is ok to store the result of

req.session.getUserId()

on each db record, so when my endpoint

"../products/all"

get hitted, I can filter all the db records by UserId and return to my front-end only the products of the given user. Is this the right way to do it? Or maybe I am missing something? Thank you in advance

Does supertoken use persistent cookies

Hi there, can Supertokens work with Nextjs and Strapi?

NextJS and strapi

I was using the session with jwt enabled , i noticed one thing that the jwt expiry is default to 1 hr, in-spite of adding ACCESS_TOKEN_VALIDITY

I am using the thirdparty recipe with react, when performing the signOut function from client and if the access token is expired , it going in to an infinite loop of refresh and signout.

Never mind the issue was the with the cookie length limit set by browsers to 4096 byte length, so it keeps retrying , after the refresh the cookie is not set due to the limit.

Cookie size

Hello everyone, I got another question. In a Express backend, can I use SuperTokens with ES6 module imports? I tried to do that but I am getting a bunch of

Error [ERR_UNSUPPORTED_DIR_IMPORT]

Importing using es6 module

I am having issue configuring dynamic origin in cors config, does super token support this

Dynamic origin issue

In the setup for password less login (only email) to control the email to a specific domain is there like access control list or should i just use emailDelivery to override the implementation to check for the email domain?

Limit email to specific domain for passwordless

Hi! I am using Angular, and I replaced the HttpClient with fetch. My understanding is that Session.init() is supposed to add interceptors to fetch to send session data along with each http request. Is my understanding correct? If it is, then how can I debug to figure out why session data is not being sent when I make a fetch request?

I have created a GitHub project. In exchange for all your help, my intent is to provide an article with a working demo for Angular/Firebase using SuperTokens so others can refer to it. However, the demo is not yet working. There are some issues with Sessions that I am unable to figure out. Here is the link: https://github.com/dleangen/supertokens-demo-1/tree/supertokens-ThirdPartyEmailPassword

Question about generating a JWT for Firebase

Questions about the docs...

Question about the Session recipe...

Hey guys, I was looking over the documentation and I couldn't find this anywhere. What's the difference between a idRefreshToken and a refreshToken?

IdRefreshToken vs refresh token