I'm new to using third party auth providers and wanted to know whether this is how it works? Let's say our app has a database entity profile which is the parent entity for many other entities that are used in the app. Do we post sign up do something like redirect the user to create profile page collect his information for app profile and save it to our database while referencing a unique field from supertokens session of the current user like user_id or user_email within the profile table so that the association between supertokens user and app profile is one to one and unique for every user?

yes. correct

@rp_st thanks

which recipe are you using?

i'm thinking of email password recipe

See this: https://supertokens.com/docs/emailpassword/common-customizations/handling-signup-success

Haha not this. I already read this. What I meant is that everywhere on youtube and in articles people only make use of the 3rd party auth provider for showcasing authentication but they never showcase how to integrate it with their own app's database and relations.

ah i see. Dont have any blog for this really.

Thats ok. Thank you.