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 all, I'm working on 3-4 projects right now, and I want to create one account per project on supertokens cloud, for some of them I won't go over free tier is this allowed to create multiple accounts by a single person?

I have supertokens core behind nginx reverse proxy. I'm forwarding these headers: proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; I get "hello" only if i remove the Host header. So I'm wondering how to bind the core instance with the A/AAAA assigned record. In the attached docs I found SUPERTOKENS_HOST but it doesnt seem to have effect on the reverse proxy, still getting HTTP Status 400 – Bad Request when forwarding the host. this is my config.yaml core_config_version: 0 host: "0.0.0.0" supertokens_host: "https://supertokens.example.com"

How can we allow multiple user roles to access a particular API? In case we want an API to be accessed by SuperAdmin along with Admin, what needs to be added in the verify_session? @verify_session( # We add the UserRoleClaim's includes validator override_global_claim_validators=lambda global_validators, session, user_context: global_validators + \ [UserRoleClaim.validators.includes("admin")] )

Hey all, is there a recommended process for debugging "Something went wrong. Please try again." on the login screen? Been getting this one recently - can't see what code change might have caused it. No error or logs in either client or server console. Network tab shows one successful request to "api/auth/authorisationalurl" and nothing else UPDATE: It was a compatibility issue somewhere between

supertokens-auth-react

,

supertokens-node

and

supertokens-web-js

. This is not the first time I've been stung and I'm wondering what might be involved in a more usable compatibility table - I'd be open to building an open source compatibility calculator if there is a need for it

How can I get the user email from its session on a backend? E.g. the email that the user used for either passwordless, login/password or social login.

Hi guys, any idea why when i'm hosting the core myself, even tho my connection string to pgsql is correct it uses in-memory db ? Is there a way to get more logs when starting up ? I only get :

Loading supertokens config.
Completed config.yaml loading.
Loading storage layer.
Using in memory storage.
Loading supertokens version.yaml file.
Started SuperTokens on localhost:3567 with PID: 15384

Is there a management background for ordinary users, such as users can change passwords, modify email？

Hi all, I'm trying to get my docker compose to run properly but have been facing the following error. Not sure why it can't detect the correct password/database:

2023-03-14 09:52:34 2023-03-14 16:52:34.972 UTC [129] FATAL:  role "doss-username" does not exist
2023-03-14 09:52:39 2023-03-14 16:52:39.086 UTC [131] FATAL:  password authentication failed for user "doss-username"
2023-03-14 09:52:39 2023-03-14 16:52:39.086 UTC [131] DETAIL:  Role "doss-username" does not exist.
2023-03-14 09:52:39     Connection matched pg_hba.conf line 99: "host all all all md5"

with the following docker compose:

version: '3.8'
services:
  # Database for developers running app locally
  doss-postgres-local:
    platform: linux/amd64
    container_name: doss-postgres-local
    image: postgis/postgis:12-3.3
    environment:
      POSTGRES_USER: doss-username
      POSTGRES_PASSWORD: doss-password
      POSTGRES_DB: doss-localdb
      PGDATA: /var/lib/postgresql/data
    ports:
      - 5432:5432
    networks:
      - app_network
    volumes:
      - doss-localdb:/var/lib/postgresql/data
    restart: unless-stopped
    healthcheck:
      test: ['CMD', 'pg_isready', '-U', 'doss-username']
      interval: 5s
      timeout: 5s
      retries: 5
    cap_add:
      - NET_ADMIN

  supertokens:
    image: registry.supertokens.io/supertokens/supertokens-postgresql:4.4
    depends_on:
      doss-postgres-local:
        condition: service_healthy
    ports:
      - 3567:3567
    environment:
      POSTGRESQL_CONNECTION_URI: 'postgresql://doss-username:doss-password@doss-postgres-local:5432/doss-localdb'
    networks:
      - app_network
    restart: unless-stopped
    healthcheck:
      test: >
        bash -c 'exec 3<>/dev/tcp/127.0.0.1/3567 && echo -e "GET /hello HTTP/1.1\r\nhost: 127.0.0.1:3567\r\nConnection: close\r\n\r\n" >&3 && cat <&3 | grep "Hello"'
      interval: 10s
      timeout: 5s
      retries: 5

Hi, is there any way to add own logger to supertokens to log requests (I am using middlleware)?