anyone have any ideas about this infinite redirec? It starts right when I launch my react js site.

it started when I was testing the signup process using the emailpassword recipe. basically I sent the confirmation email, used sql to delete the newly created user record before verifing via email, and now when I launch the site I get this infinite redirect.

it also happened about the time that I tried starting to remote debug for the first time on the site. Could it be something with my run configuration?

I found a resolution - it had something to do with the or cookies because I cleared all browser data from the last 24 hours and the redirect issue stopped

the issue starts again when using VS codes debug feature. Any time I run the site via the debugger, I get that redirect issue. anyone know how to set up a debug configuration that works with supertokens?

this is my launch.json

Username in payload

Does the react form take good care of security? Like SQL injection etc

Do you guys in supertoken has any limit for string character in JWT token?

hello, [Pardon in advance if this has been asked earlier in some thread, haven't come across any] Context: we are using self hosted supertokens core, and golang sdk in the backend auth service presently the OTP flow is : 1. front-end client (the react single-page-app [spa]) request signs in/up by calling the auth backend service 2. auth backend communicates with supertokens core where the OTP is generated 3. OTP is communicated to the concerned phone number 4. the spa calls the OTP consume API with the generted OTP and according the sign in/up is handled Now, we need a way to bypass out QA testers , say in staging/dev/qa environment, for a fixed set of numbers, only a fixed OTP is generted. So, any suggestions for this?

Bypass some passwordless users

Hi, Sorry in advance if this has already been asked, I seached through the search engine but didn't find the information. I'd like to know if there is a way to sign in with an email or a custom username? The

/recipe/signin

API request parameters are only

email

and

password

but maybe there's a way to extend something and supports

email

or

username

parameters? Thanks in advance for your replies and suggestions 🙂

Hi @porcellus @nkshah2 . Nice to meet you. How are you doing?. My name is Araki from Japan. As a senior fullstack&Blockchain engineer, I am very interested in your company. In particular, supertoken is very interesting tech for me. I have some experience in User Authentication including OAuth, OAuth2, SSO, 2 Factor Authentication and so on. So I think, we can work together. I already apply for your company. but I didn't get the any response after introduction meeting. I really want to work with your company. If you are available, Please contact me. Thanks.

Hi porcellus8953 nkshah24169 Nice to

it also happened about the time that I

Does the react form take good care of

Do you guys in supertoken has any limit

Hi, im using supertokens with my app. Backend - Express, Frontend - React. Is there any way to set Login Page to another language? Lets say german.

Hi, I'm trying to override the

ThirdPartySignInUpPOST

function for Passwordless sign in. This is my recipe list

This is the function which return the override:

It's not triggerring after

signinup/code/consume

api is successful? Am I doing something wrong?

Hello @nkshah2 & @porcellus , I don't know if you're already on it, but the algolia search doesn't work anymore in the supertokens docs

When modifying the signInUp form as described in the guide in the link, is it then possible to add a validation function that checks that the value of two fields are equal? For example for verifying that the user typed the correct password, they have to type it twice. (same with email) https://supertokens.com/docs/emailpassword/common-customizations/signup-form/field-validators

Hello @nkshah2 & @porcellus , I have 1 question about the signup endpoint. How to protect it if we don't want to be spam by hacker which will try to create a user ?

Hello nkshah24169 porcellus8953 I have 1

Hi. I have a problem while doing fetch from the front end to my backend I get 401 non-authorize. In docs, it said that if 8using fetch no actions are needed, what I'm missng

Routing too quickly?

I see in the docs for ThirdPartyEmailPassword Recipe there is the option to replace individual react components within the signin/up form Does supertokens (react) give the ability to completely replace the component for the frontend? Or would I need to use the backend's api to use my own frontend component?

Just FYI -- TOTP is mispelled on the product roadmap on the supertokens site https://supertokens.com/product-roadmap

Some feedback -- if a user hits the /auth/signout route WITHOUT the right cookies (i.e. missing a refresh token cookie, or no cookies at all) the backend will 200 OK. If you enable debug logs it'll show something is amiss, but the 200 OK is very misleading. Similar on the frontend -- it'd be nice to get verbose output upon misconfigured

SameSite

and cookies not being stored properly. Cost 2-3 hours of dev time spinning wheels yesterday in local environment trying to figure that one out. Signout was simply doing nothing and it wasn't obvious what was broken.