I just setup Supertokens and got it linked with my db and I got the init command added to my api. Do I have to create all the routes for my API or is there something i'm missing?

I'm writing microservices in go and want to migrate to using super tokens (self-hosted). What is the "best practice" to authenticate requests on different services? Previously using AWS Cognito which gave me JWKs to validate requests.

I discovered today that Playwright might give devs access to the browser's cookies. (Would have to confirm on my own.) If they do, it could be a great tool for testing example repositories since it also enables devs to disable JavaScript in the browser during end to end testing. If a set of standard test cases could be created, they could be run against any example repo to make sure everything still works as expected during repo NPM package upgrades, etc. Hoping to look into this sometime within the next 4 months. But sounds pretty exciting (since it would take away a lot of manual work).

Hello! I am trying to implement OTP in my Android app but the SuperTokens object isn't saving the session information. I am wondering if I initialized SuperTokens incorrectly (or something else) SuperTokens.Builder(applicationContext, apiDomain) .apiBasePath("/api/auth") .build() I can hit apiDomain on my local machine so we can assume this is correct I can see all the session data that I want in the response in logcat but I somehow can't access it in the SuperTokens object

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!

.local tlds should be allowed as website and apidomain names

What's the best way to debug why a user can't log in after getting the SMS code with passwordless? (Once they enter the code, it says "Error" even though they are a user)

hey guys, I hope you're doing well. I'm reaching out because I've encountered an issue with my Django application that involves the @verify_session() decorator provided by SuperTokens. Here's a snippet of my code:

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.

Ok I am using this example, to access the user role using the jwtpayload, https://supertokens.com/docs/emailpassword/common-customizations/sessions/user-information-front-end. But I run into the error jwtpayload.role is not part of the properties