Hii everyone, I have three apps running on https, and self hosted supertokens core that too running on https api.example.com example.com app.example.com I can login to example.com, it works. But when I go to app.example.com, I can see the cookies being attached to the http req, but api.example.com throws unauthorised. I have no idea what to do now. This is what I see on app.example.com

hey team, I changed some custom claims in the access token payload, since then, I dont seem to get the

Session.doesSessionExist()

to be true. I've added an array to one of the custom claim. Not sure if thats supported

Hi @rp_st! I have an issue setting up the User Management Dashboard. I followed the guide at https://supertokens.com/docs/userdashboard/about to run it locally (using Python/FastAPI). It all worked, the page loads, but I am unable to create a user. Running the suggested

curl

command results in a "Not found". Same happens on a password reset attempt. What could be the cause and how do I fix this?

Hi, did anyone manage to secure command line applications using SSO with Supertokens ?

I am working on a frontend app talking to a supertokens backend and implementing OTP login with phone works like a charm, I wanted to read the JWT in the client so I had to add the session recipe to the backend and also call session.init in my client, this worked also like a charm and I was able to read the JWT. However when I do not log in using phone and OTP, I still want to have a JWT session for anonymous users but the Session.getUserId() returns false Is there anything more to it for session based authentication other than just having Session.Init() in the recipes array in the client and also in the backend? BTW: just wanted to shout out that other than this, using supertokens has been so smooth

Is there already a solution to using supertokens with tRPC? Thanks in andvance

Hi! I've implemented the SuperTokens login to a vue3 project and it works beautifully, but am greeted with lint-like errors for every class across the app, and I've isolated it down to the

supertokens-auth-react

package that appears to be causing it. Any info or advice to clean these errors would be super helpful 😊 Additionally here is the inline error

Type '{ class: string; }' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
  Object literal may only specify known properties, and 'class' does not exist in type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.ts(2322)
index.d.ts(3176, 13): The expected type comes from property 'div' which is declared here on type 'IntrinsicElements'

java
Error: Initialisation not done. Did you forget to call the SuperTokens.init function?

I keep getting this error when going to my /testauth path but I did call the function before the route

import { verifySession } from "supertokens-node/recipe/session/framework/express/index.js";

router.get("/testauth", verifySession(), (req, res) => {
  if (req.session == null) {
    res.send({ error: "Must be signed in", code: "401" })
    return
  }
  let userId = req.session.getUserId();
});

Is there a way to remove the "Powered by supertokens" text from the bottom of the sign up / sign in forms?

Google login client id and secret