Rishabh Poddar

## Enabling / disabling automatic account linking By default, we want to keep it disabled (due to the complexity it presents). However, we allow users to enable it on a...

## Fetching info about user from non auth recipes ~Ideally, there should be no extra info associated with the recipe user ID, and all info should be associated with the...

## Affect on user pagination and count functions The `all_auth_recipe_users` now contains users that are recipe user IDs (non linked) and primary user IDs. So the return type of the...

## Known issues: - (RESOLVED) If the user signs up with email password and their account is not yet verified, the user ID returned will != the one after their...

## Change to reset password flow If attacker signs up with social provider with email `a` (which they have access to), and then creates another email password account with email...

## New emails On account linking, we should send an email to the user saying that they just logged in via XYZ, and if it wasn't them, then they should...

# Additional considerations: - Implicitly creating email password user (if they have an existing account already with the identifying info with another recipe) if reset password is being done ->...

If the account to be linked has existing non auth recipe info (like in metadata), that info is kept as is and nothing is done with it. We don't even...

Have you tried to import like `import * as SuperTokens from 'supertokens-website'`?

Hmm. We will have to look at how it's built. But this is probably not a priority for us at the moment, unless more people face this issue. However, please...