Skip to main content

Implementing account deduplication

The approach to implementing account deduplication is to override the backend functions / APIs which create a user such that:

  • We check if a user already exists with that email.
  • If a user does not exist, we call the original implementation; Else
  • We return a message to the frontend telling the user why sign up was rejected.

Add the following override logic to ThirdPartyEmailPassword.init on the backend

import ThirdPartyEmailPassword from "supertokens-node/recipe/thirdpartyemailpassword";

ThirdPartyEmailPassword.init({
    override: {
        functions: (originalImplementation) => {
            return {
                ...originalImplementation,
                emailPasswordSignUp: async function (input) {
                    let existingUsers = await ThirdPartyEmailPassword.getUsersByEmail(input.tenantId, input.email);
                    if (existingUsers.length === 0) {
                        // this means this email is new so we allow sign up
                        return originalImplementation.emailPasswordSignUp(input);
                    }
                    return {
                        status: "EMAIL_ALREADY_EXISTS_ERROR"
                    }
                },
                thirdPartySignInUp: async function (input) {
                    let existingUsers = await ThirdPartyEmailPassword.getUsersByEmail(input.tenantId, input.email);
                    if (existingUsers.length === 0) {
                        // this means this email is new so we allow sign up
                        return originalImplementation.thirdPartySignInUp(input);
                    }
                    if (existingUsers.find(i => i.thirdParty !== undefined && i.thirdParty.id === input.thirdPartyId && i.thirdParty.userId === input.thirdPartyUserId)) {
                        // this means we are trying to sign in with the same social login. So we allow it
                        return originalImplementation.thirdPartySignInUp(input);
                    }
                    // this means that the email already exists with another social or email password login method, so we throw an error.
                    throw new Error("Cannot sign up as email already exists");
                }
            }
        },
        apis: (originalImplementation) => {
            return {
                ...originalImplementation,
                thirdPartySignInUpPOST: async function (input) {
                    try {
                        return await originalImplementation.thirdPartySignInUpPOST!(input);
                    } catch (err: any) {
                        if (err.message === "Cannot sign up as email already exists") {
                            // this error was thrown from our function override above.
                            // so we send a useful message to the user
                            return {
                                status: "GENERAL_ERROR",
                                message: "Seems like you already have an account with another method. Please use that instead."
                            }
                        }
                        throw err;
                    }
                }
            }
        }
    }
})

In the above code snippet, we override the thirdPartySignInUpPOST API as well as the thirdPartySignInUp and emailPasswordSignUp recipe function.

The thirdPartySignInUpPOST API is called by the frontend after the user is redirected back to your app from the third party provider's login page. The API then exchanges the auth code with the provider and calls the signInUp function with the user's email and thirdParty info.

The emailPasswordSignUp function is called by the API that handles email password sign up.

We override the thirdPartySignInUp recipe function to:

  • Get all ThirdParty or EmailPassword users that have the same input email.
  • If no users exist with that email, it means that this is a new email and so we call the originalImplementation function which creates a new user.
  • If instead, a user exists, but has the same thirdPartyId and thirdPartyUserId, implying that this is a sign in (for example a user who had signed up with Google is signing in with Google), we again allow the operation by calling the originalImplementation function.
  • If neither of the conditions above match, it means that the user is trying to sign up with a third party provider whilst they already have an account with another provider or via email password login. So here we throw an error with some custom message.

Finally, we override the signInUpPOST API to catch that custom error and return a general error status to the frontend with a message that will be displayed to the user in the sign in form.

We also override the emailPasswordSignUp recipe function to perform similar checks:

  • Get all ThirdParty or EmailPassword users that have the same input email.
  • If no users exist with that email, it means that this is a new email and so we call the originalImplementation function which creates a new user.
  • Else we return the status that tells the user that the email already exists.
Multi Tenancy

For a multi tenant setup, the customisations above ensure that multiple accounts with the same email don't exist within a single tenant. If you want to ensure that there is no duplication across all tenants, then when fetching the list of existing users, you should loop through all tenants in your app, which you can fetch by using the listAllTenants function of the multi tenancy recipe.

Which UI do you use?
Custom UI
Pre built UI