I'm using NextJS's API routes. The API cannot find the route: http://localhost:3000/api/auth/session/refresh . Do I need to add interceptors? I think the latest version of Supertokens removed the need for adding interceptors right? Using "supertokens-auth-react": "^0.27.3", "supertokens-node": "^12.1.1",

Hello Everyone, I'm new to SuperTokens, right now I'm trying to get it work with Sapper app and importing "supertokens-node/recipe/session" crashes my server somehow. Does anybody have any idea why this would happen?

Has anyone managed to get supertokens working with next.js v13 app directory?

Question - Is there a way to use multiple cookie domains on one port. the use case we have is the same api server, but we have 2 frontend services on different domains

I am using the supertokens middleware in our backend; and seeing this error. Is it something that I should handle? {"type":"SessionError","message":"Failed to verify access token","stack":"Error: Failed to verify access token at Object. (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:89:19) at Generator.next () at /usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:44:75 at new Promise () at __awaiter (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:26:16) at Object.getInfoFromAccessToken (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:57:12) at Object. (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/sessionFunctions.js:105:55) at Generator.next () at fulfilled (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/sessionFunctions.js:15:36) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)","errMagic":"ndskajfasndlfkj435234krjdsa","fromRecipe":"session","isBoom":true,"isServer":true,"data":null,"output":{"statusCode":500,"payload":{"status":500,"error":"Internal Server Error","message":"An internal server error occurred","code":"UNKNOWN","data":null},"headers":{}}},"msg":"Failed to verify access token"}

Hey, I've been using supertokens-auth-react with Vite and the styles don't seem to be loading in. Is there something I might be potentially doing wrong?

hello, im getting 401 unauthorized when im trying to use the verifySession() middleware, any idea what can the problem be? I'm using EmailPassword recipe. Also I have another question, can I use the SessionRequest object in a js object not ts ? im trying to get the token payload

I also get a 403 forbidden error when trying to call my FastAPI backend, but presume that's because the user is logged in but not yet verified.

How do we use supertokens with sveltekit??

Hello again people, context: we are using the self-hosted version of supertokens core in kubernetes (with the help of helmchart mentioned here https://github.com/supertokens/supertokens-docker-postgresql/tree/master/helm-chart ) with

thirdpartypasswordless

recipe , in

golang

backend sdk (with gin framework) now, in the refresh session flow, the call to core at

/recipe/session/refresh

from the golang-sdk is breaking i.e., for i tried manually calling supertokens core via cURL with:

curl --request POST 'http://supertokens:3567/recipe/session/refresh' --header 'api-key: <api-key here>' --header 'rid: session' --header 'content-type: application/json; charset=utf
-8' --header 'cdi-version: 2.14' --data-raw '{"refreshToken": "<refresh token here>", "enableAntiCsrf": false}'

the response returned by core is

{"status":"UNAUTHORISED","message":"java.lang.IllegalArgumentException: Illegal base64 character 25"}

So any help would be appreciated PS: when I tried the refresh flow locally, with docker image of supertokens core ran locally, the same call to

/recipe/session/refresh

via golang-skd is getting response OK (with the same sdk version of supertokens in golang)