Hello, i'm having an issue with the integration to NestJs. I'm getting a blank (white) screen when i try to load the dashboard... Everything seems to work fine when i call the signup api from postman though... Any ideas please?...

I am setting up something wrong with supertoken and I have no clue how to fix this? Does anybody have a clue? My first error in the console.log is this in the attached image.

Hello 👋 I want to add metadata to my existing users. However, all of the python examples I can see are about running init() and sdk functions from within flask/fastAPI/django. Is there a way for me to use supertokens sdk on a standalone python script, point it to the supertokens instance I have on my backend (postgres), and add the metadata? My hacky solution is to directly update the

user_metadata

table on postgres, but that's a rast resort

Hello, I have been having trouble with getting Next.JS App Directory SSR to work properly. I've been following the documentation on https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre and looked at the repository (https://github.com/supertokens/next.js/tree/canary/examples/with-supertokens/app). (I last checked these pages and followed them today, 2/9/2024) The components sessionAuthForNextJS.tsx and tryRefreshClientComponent.tsx are the same and I followed the code stated in home.tsx. Looking at my configuration files, they seem to be correct. When I attempt to log in, it works just fine and such. Then if I try to go to my dashboard, which has the SSR authentication requirement, I will first be redirected to the auth page for a moment then pushed to the home page '/'. Then every other attempt of trying to go to the dashboard will just continue to redirect me to the home page '/'. If convert the SSR pages into their client side version then it works just fine, however I want to use SSR for increased performance and user experience. I then got confused with the middleware, thinking it was part of the SSR before realizing it was only for APIs, but the middleware approach did fix my issues, until expiration occurred and I'd get a "Authentication required" message. As a temporary fix to this, the user would need to go back to the home page and then they'd be able to go to the dashboard and its sub pages. This sort of works but there are pages where users would go straight to a sub page within the dashboard, so they'd get this message often. Figuring out that the middleware was only for APIs, I went back and commented it out. I am now at square one with SSR authentication again and can't seem to figure out why I am only redirected to the home page and never allowed into my dashboard.

Dears, I have an issue to authenticate with hasura, as hasura does not accespt the jwt to be in the cookie and needs it to be in Authorization header , the documentations states we can expose the token to the browser using exposeAccessTokenToFrontendInCookieBasedAuth: true, in the session.init , but when I do that the CORS gives error Access-Control-Allow-Origin not included in the header although the configuration of the cors module is correct :app.use(cors({ origin: "https://url", allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], credentials: true, })); I would appreciate your help

Implementing a refresh token flow as explained in https://supertokens.com/docs/session/common-customizations/sessions/ssr#3-implementing-the-refresh-session-flow-refresh-session-pagr causes the whole web app to 'flash' every time a token is refreshed, because we navigate to the /refresh-session page (using Remix in my example). Is there a way to refresh the token on the server during the request instead of redirecting to a front-end page that needs to do an API call and redirect back?

In prebuilt UI , how can i provide the clientType query param in the authorisation Url as it is not automatically considering the clientType and throwing error in the backend as I am using three configs of google namey web, android, and iOS

Hi, Our current functionality is build on Flask, but flask is not supporting Async completely which is required for one of our requirements. So, we were planning to move to Quart framework. So, the question is, SuperTokens support Flask, FastAPI and Django REST framework Out of the Box. Can we do to run SuperTokens on Quart as well?

Hi! I'm trying to implement unified user authentication for multiple private services. I was imagining that each service would provide the users credentials alongside with a service identifier, which would then get packed into the JWT as the

aud

claim. The client would then use the JWT for requests with the service thereafter. I took a look at https://app.swaggerhub.com/apis/supertokens/FDI/1.18.0#/EmailPassword%20Recipe/signIn for the prebuilt backend, but I couldn't find a way to pass this id anywhere. What's the easiest way for me to do this?

Hi, we have implemented thirdpartyemailpassword recipe along with emailverification recipe. But for some users, they didnt verified their emails with the login provider. So their emails not marked as verified. For those users, when we try to call an api, we are getting claims not verified error. How to get access the api without needing to verify their emails?