Hi I am trying Supertokens social login using Fast API and custom UI. Everytime I am trying to get an access token, I am getting an error in

singinup

API.

{"status":"FIELD_ERROR","error":"'access_token'"}

Any guide to setting up nginx reverse proxy for the backend server "not core"? I keep on getting bombarded by cors errors

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

Greetings, does this works with WordPress?

This is the response I get when I click the Sign In With Google button or Facebook (see attached images). My frontend is still hosted locally: http://localhost:3000 But my backend is forwarded with: https://fccd-****ngrok.io Supertokens Code: Backend Node (config.ts):

export const SuperTokensConfig: TypeInput = {
  supertokens: {
    connectionURI: "http://127.0.0.1:3567",
  },
  appInfo: {
    appName: "SuperTokens Demo App",
    apiDomain: "https://fccd-****.ngrok.io",
    websiteDomain: "http://localhost:3000",
},
...

Frontend React(config.tsx):

export const SuperTokensConfig = {
    appInfo: {
        appName: "SuperTokens Demo App",
        apiDomain: "https://fccd-****.ngrok.io",
        websiteDomain: "http://localhost:3000",
    },

Cors:

app.use(
  cors({
    origin: "http://localhost:3000",
    allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
    methods: ["GET", "PUT", "POST", "DELETE"],
    credentials: true,
  })
);

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"}

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

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?

Missing Cookies