Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guides

getting this error in the console on the client side Access to fetch at 'https://api-development.bitcoinerfreelance.com/auth/session/refresh' from origin 'https://development.bitcoinerfreelance.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. Here is my Cors implementation on the back end app.use( cors({ origin: websiteDomain, allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], methods: ["GET", "PUT", "POST", "DELETE"], credentials: true, }) ); and my Supertokens init supertokens.init({ framework: "express", supertokens: { // TODO AARON - in production need to swap this with the connection for supertokens connectionURI: configData.superTokens.connectionURI, apiKey: configData.superTokens.apiKey, }, appInfo: { appName: "Bitcoiner Freelance", apiDomain: apiDomain, websiteDomain: websiteDomain, apiBasePath: "/auth", websiteBasePath: "/auth", },

I want to create a new user context that includes a request in golang, how can i do that?

I'm running a Supertokens managed instance in production (on my Flask Python backend, which is hosted on Google Cloudrun). Since it's inconvenient to access the dashboard URL through cloudrun, I found I can run my backend locally (with production flags set) and then access the production dashboard at http://localhost:8000/auth/dashboard Is this recommended / might this interfere with the instance running on prod? (e.g. if limited connections to the Supertokens instance is permitted at once)

@rp_st hello, I was using the supertoken 3.14 version it was working fine then switched to latest version it broke down and i am getting this error recently org.postgresql.util.PSQLException: ERROR: column "use_static_key" of relation "session_info" does not exist

Hello everyone I have been trying to find a solution for many days, but without success. Please help me fix this error: ( ERROR [ExceptionHandler] Please make sure that the apiDomain and websiteDomain have correct values)

I'm new to setting up oauth providers and such, and am currently getting back the no email given by provider error from my Azure AD integration. Are there any common gotchas that might cause this type of error? I'm sure it's something simple in my Azure AD app registration that I'm no doing right

Hi, I have a simple web application and I am trying to perform login and get session information like getting the access token When I try to run the code below, it show error which is no instance of session found. Make sure to call session.init method. How should I be logging in and getting the session object? session_provider :async() => { supertokens.init({ appInfo: { apiDomain: "https://aarron28.com", apiBasePath: "/auth", appName: "Test App" }, recipeList: [ supertokensSession.init({ tokenTransferMethod: "header" // or "cookie" }), supertokensSession.init(), supertokensEmailPassword.init(), ], }); var aaa = await supertokensEmailPassword.signIn({ "formFields": [{ "id": "email", "value": "lucas333" }, { "id": "password", "value": "pas123" }] }); supertokensSession.getAccessToken(); return aaa; }

Hey, I have a website and a chrome extension. What i want to do is when the user logins inside the website, he should automatically login inside the extension as well. This is a business project.

I just posted to production. Been developing localhost with nextjs. When in production I'm getting this error:

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

I'm wondering if it has something to do with

NextCors

middleware? Any ideas?