@User What is the console log for

userId

?

is it a UUID?

and you may want to do

let user = await getUserById(userId);

i.e. add an

await

Ok. the await worked. thanks.

So where in the documentation is getUserById? Did I miss it?

Yea the docs for that are missing..

Ok. 🙂

Is this project brand new? Is that why?

yes. It is relatively new!

So better docs soon? 🙂

yes. very soon 🙂

within the first two weeks of jan

Sounds good.

So is user management going to be an option?

Also, does session timeout automatically or can we set a timeout value?

you can set the timeout value: https://supertokens.io/docs/emailpassword/common-customizations/sessions/change-session-timeout

So lowering refresh_token_validity will force user to reauthenticate?

yes. it's basically the session inactivity timeout

so if that value is = 10 days, then a user will be logged out only after 10 days of inactivity.

How short can I set it for testing purposes?

Can I set it to hours or minutes?

yes. the unit is in mins. And the minimum value is 0.0166667 mins (1 sec)

Ok. I'll check it out. Thanks

👍

Hey, I had a question regarding the flow & structure. So with the default setup, after a user signs up, where is the information stored (the email and password hash)? Does it get persistently stored somewhere by default or do we need to add another request when the Sign Up button is clicked to our own API to save the user credentials

If you are using the self hosted version, the email and password hash are stored in your db (the one you have connected supertokens core with). If on the other hand, you are using our managed service version, it gets stored in a dedicated database we provide for your instance of the core.

@User I gotcha. I'm gonna go with the self-hosted DB. So in the case that I have other information I want associated with a

User

like bio, email, avatar, for example, what would you suggest on how to set that up?

Because currently just a user ID, email, and password hash are stored via supertokens right?

> Because currently just a user ID, email, and password hash are stored via supertokens right? Yes. To store other info post sign up, you can override a callback in your node code when initing SuperTokens: https://supertokens.io/docs/emailpassword/common-customizations/signup-form/adding-fields#handle-form-fields-on-successful-sign-up As you can see in the above link, you can override

handleCustomFormFieldsPostSignUp

, which will be called on successful signup. The arguments to this function is the

user

object (

user.id, user.email

). And any extra form fields you may have added to the sign up UI. Using the above, you can store any info associated with your user in a separate table, controlled by your app (and not supertokens).