Oh, ok, but I am signing up with email & password

The config you have done seems to be done correctly.

Can you do a console log at the start of the

validate

function?

Hm, nothing is logged

hmmm

emailPasswordSignUpPOST: async (input) => {
  console.log('before');

This is not triggered either so I might have broken something else

Do you have two

supertokens.init

calls on the backend?

Only 1 per "api page"

Makes sense.

Free for a quick debug call?

Yawn, restarted the next-server and it works now...

oh haha.. well..

Sorry, and thanks!

no worries 🙂

can we disable the signup feature ?

Yes. Which recipe are you using?

email and password recipe

ok. So first, you want to disable the sign up API on the backend: https://supertokens.io/docs/emailpassword/advanced-customizations/apis-override/disabling Then you want to override the react components on the frontend to not show the button to switch to sign up and also provide

null

to the component for the sign up form: https://supertokens.io/docs/emailpassword/advanced-customizations/react-component-override/usage

got it thanks

👍

Does anyone know if we can disable email validation and be able to just have like a username? So instead of "username@domain.com", it can just be "username"? Is there a way to change password requirements?

I'm not sure I'm qualified to answer, but is it that you just don't want to require an email or is it that you want to use a different uid?

I think the answer is that you can do it any way you want, but what you want isn't the out of the box experience, so you are going to have to code a bunch on your own.

@User yes. You can change the validation logic: https://supertokens.io/docs/emailpassword/common-customizations/signup-form/field-validators#changing-the-default-email-and-password-validators

However, if you do what you are saying, then how will the reset password flow work? Cause you won't have the user's email.

Awesome. Thank you! Also, thats a good point. I don't plan on having that in my app. I just like being able to have a generic username for credentials

Oh okay.. so if you don't want reset password, then you can modify the default validators as stated in the above link and it should work..

Though one small issue is that the

user

object returned by our functions will still have the field as

email

(which will actually be that user's username).

Okay. I'll play around with it. Thank you!

Hello everyone, I have a problem when I override the sign up and create new session functions : When a user registers I want to save his information in my database (for example firstname, lastname). Then his information will be added in the token when creating session. The problem is that I make a save in the database after

await originalImplementation.signInUpPOST(input);

. When I want to fetch my user at create session time the user is undefined. So my firstname lastname is not added in my token How can I do ?