Hey everyone, I'm facing an issue with my Express backend setup along with Supertokens for session management. Here's a snippet of my backend code:

javascript
import express from "express";
import { verifySession } from "supertokens-node/recipe/session/framework/express";
import { SessionRequest } from "supertokens-node/framework/express";

let app = express();

app.post("/like-comment", verifySession(), (req: SessionRequest, res) => {
    let userId = req.session!.getUserId();
    //....
});

I've added

verifySession()

to ensure that only authenticated users can access the

/like-comment

route. However, I'm having trouble accessing this route from the front-end using Axios. I've wrapped my component inside

SessionAuth

so that logged-in users have access, but I keep receiving a 401 error. Could anyone guide me on how to properly access this route from the front-end using Axios and ensure that the user is authenticated? Thanks in advance!

hi there i am trying to get the user info but getting 404 error in next js please anyone tell me what i am doing wrong i am refering this doc - https://supertokens.com/docs/thirdpartypasswordless/common-customizations/get-user-info and here is my code

Hey guys, is there any docs or blogs on setting up any reverse proxy to the backend API? Or somewhere to get me to start?

Hi, I have a situation where I limit the user to add X number of files to the server. I have created a permission of 'add_files', but how can I save the amount of files he can add to him self? is there a metadata place where I can put this to users that has

add_files

permission? I want to avoid:

add_files_1

,

add_files_2

,

add_files_3

and so... Thanks

Hi, i'm using custom UI - react. i have supertokens core installed in local. used 'supertokens start' to run it. when i ping curl http://localhost:3567/hello i'm getting reply hello, but in the app when i try to http://localhost:3001/auth/signup, it shows 500 status code on sign up endpoint and also tried in postman it's throwing error as TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11372:11) at processTicksAndRejections (node:internal/process/task_queues:95:5) at sendRequestHelper._a (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:51:36) at Querier.sendRequestHelper (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:326:32) at Querier.getAPIVersion (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:41:38) at sendRequestHelper._a (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:177:38) at Querier.sendRequestHelper (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:326:32) at Querier.sendGetRequest (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\querier.js:173:40) at Object.listUsersByAccountInfo (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\accountlinking\recipeImplementation.js:161:26) at Recipe.isSignInUpAllowedHelper (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\accountlinking\recipe.js:280:25) supertokens core is running as you can see in the image. if anyone facing same issue and got it resolved kindly share the solution.

@rp_st I am using ThirdPartyPasswordless recipe, I want to do certain steps post successful login(otp verification etc) but before the session gets created. If this is achievable, Where should i place my logic(which function override?)

Hi Team, We are getting a KeyError 'access_token' on our Flask backend when fetching profile info via Google: supertokens_python/recipe/thirdparty/providers/google.py in get_profile_info at line 58 We think it is likely that the signup API is being called twice and returning a 500 response from Google the second time, which means that the auth_code_response does not have the 'access_token' key, and instead returns the following error: { error: 'invalid_grant', error_description: 'Bad Request' } We have looked at this thread https://discord.com/channels/603466164219281420/1113510798736752692 and its related GH issue (https://github.com/supertokens/supertokens-auth-react/issues/707) but haven't been able to come up with a solution. We also cannot reliably reproduce this error. Could we get some support / should the API be catching this to avoid the KeyError? Thank you in advance!

Hi, I'm trying to setup the dashboard. I'm trying to create a user using the CLI command but I'm getting

{"status":"INVALID_EMAIL_ERROR"}

curl --location --request POST 'https://xxx.aws.supertokens.io/recipe/dashboard/user' \
--header 'rid: dashboard' \
--header 'api-key: <YOUR-API-KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{"email": "<YOUR_EMAIL>","password": "<YOUR_PASSWORD>"}'

My email ends in

.dev

is there some validation going on?

Hi everyone, I'm new to the MERN tech stack and I'm seeking input on my current approach. I'm utilizing Cloud services, which are free for up to 5,000 monthly active users. To elaborate, SuperTokens will handle the storage of user details for signups, whether through standard login or social login, allowing me to oversee user interactions via the designated dashboard. My plan is to replicate each user's information stored in SuperTokens and archive it in my MongoDB users collection for potential future requirements. Is this duplication strategy advisable, or do you have any recommendations? Thanks in advance.

Is there a way to restrict sign in to allow emails only from a specific domain when using sign in with google @rp_st