I know. Only I don't know how get data when user's signing up through a provider. I can do this in getProfileInfo in custom provider but I don't have unnecessary requests during login and if user will change e. g. pseudonym, then data will change unnecessarily and the user may become frustrated and delete the account, so I can lose users and have unnecessary requests. Because of I want get data about users from providers only during sign up, but I don't have how do this.

Hi 👋 do you know how to combine Supertokens and Nextjs when internalizationed routing (https://nextjs.org/docs/advanced-features/i18n-routing) is used? 🙂 For the moment, I can only use the path

my.domain.local/auth

while I would like to use also

my.domain.local/[lng]/auth

(*e.g. *`my.domain.local/fr/auth`) but also

my.domain.local/auth

(default route) in an automatic way as NextJS does when using the intl routing feature.

Hi SuperTokens team, I am using Supertokens with NestJs. All my APIs are rate limited via https://docs.nestjs.com/security/rate-limiting. Do you have any clue to let the SuperTokens middleware (for calls like e.g. /auth/signin) be aware of these rate-limiting settings?

Hi, I'm trying to integrate with the AWS HTTP API Gateway built-in JWT authentication and am receiving the following error: Bearer scope="" error="invalid_token" error_description="no "kid" provided in the JWT" Is there a way to add this? I tried adding it like the example mentions to add the Audience but then it's in the userData instead of, I assume, the outer payload.

Is there already a solution to using supertokens with tRPC? Thanks in andvance

Hi! I've implemented the SuperTokens login to a vue3 project and it works beautifully, but am greeted with lint-like errors for every class across the app, and I've isolated it down to the

supertokens-auth-react

package that appears to be causing it. Any info or advice to clean these errors would be super helpful 😊 Additionally here is the inline error

Type '{ class: string; }' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
  Object literal may only specify known properties, and 'class' does not exist in type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.ts(2322)
index.d.ts(3176, 13): The expected type comes from property 'div' which is declared here on type 'IntrinsicElements'

Hi! I was interested in using Supertokens for a side project. Right now, my strategy is to use the pre-built UI to accelerate setting up the app and then switch to a custom auth UI down the road. Is this an easy switch to make?

Hi, hope you all are fine ! I got

{
message: "try refresh token"
}

on the

/auth/dashboard

Hi! I'm trying to test the Passwordless (SuperTokens 4.2) recipe on Postman, but I get a 400 response: "Please provide exactly one of email or phoneNumber". I've followed the example on https://supertokens.com/docs/passwordless/testing/testing-with-postman. What could I be doing wrong?

Hi, I'm looking to implement "web3" authentication. Is there anything like that integrating with SuperTokens already? If not, I would appreciate any pointers to the best way for me to implement it myself. (By "web3" auth, this is what I mean: on a new session the server sends a challenge to the user client who signs it with their crypto wallet and sends back to the server. The server compares the signed challenge with the previously registered public keys for the user. Here's an in-depth "vanilla" integration example https://www.toptal.com/ethereum/one-click-login-flows-a-metamask-tutorial)