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?

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

Has anybody seen this error? API input error: Please make sure to pass valid URL query params 2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Started", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:321:26" sdkVer: "13.0.2"} 2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Error is from SuperTokens recipe. Message: API input error: Please make sure to pass valid URL query params", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:323:30" sdkVer: "13.0.2"} 2023-02-25T22:28:00.818Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "errorHandler: Sending 400 status code response", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/supertokens.js:325:34" sdkVer: "13.0.2"} 2023-02-25T22:28:00.819Z com.supertokens {t: "2023-02-25T22:28:00.818Z", message: "Sending response to client with status code: 400", file: "/Users/dave/Code/node_modules/supertokens-node/lib/build/utils.js:133:14" sdkVer: "13.0.2"} I'm getting it when trying to implement Sign In with Apple. I'm POSTing to /api/auth/callback/apple a

state

and a

code

value Everything seems like it should work.

Hi @rp_st For refreshing the session , I am able to use the same refresh token multiple times for getting new access token if I pass that as Authorization header Whereas if I pass same refresh token twice as cookie then it says Token theft detected and on third time it says : Unauthorized Can you please tell why the flow differs in both cases that is Authorziation header and cookie ?

I'm using Nestjs as backend, with both rest and graphql implementation. How should I set the token in graphql playground?

I'm using Next.js (frontend and SSR) + FastAPI (as a traditional backend). The FastAPI backend is the same application logically (same domain and can be called from the browser directly). Do you recommend using a JWT session for this architecture, and sending the JWT to FastAPI?

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)

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

does super tokens work with svelte/kit for frontend?