Skip to main content

User Context


This feature is only available for SDKs versions:

  • NodeJS >= v9.0
  • Python >= v0.5
  • GoLang >= v0.5

How does it work?#

This is a powerful concept that allows you to pass information across recipe and / or API functions so that customisations can be made based on a specific "execution context".

For example, you may want to disable creation of a session during sign up so that the user has to login again post sign up. In order to do that, the createNewSession recipe function (from the Session recipe) will have to know that it's being called from the sign up API and return an empty session (which is equal to no session). This is as opposed to it being called from the sign in API, in which it should continue with normal functionalty.

In order to achieve this, all the API interface and recipe interface functions take a parameter called userContext which is by default an empty object. When overriding the functions, you can add anything in this object and that information is carried onto the next set of functions being called in the API

Example use#

Let's take the example mentioned above and implement it in the context of this recipe. First, we override the sign up recipe function to add information into the context indicating that it's a sign up call:

import SuperTokens from "supertokens-node";import ThirdParty from "supertokens-node/recipe/thirdparty";
SuperTokens.init({    appInfo: {        apiDomain: "...",        appName: "...",        websiteDomain: "..."    },    supertokens: {        connectionURI: "...",    },    recipeList: [        ThirdParty.init({            signInAndUpFeature: {                 providers: [/*...*/]            },            override: {                functions: (originalImplementation) => {                    return {                        ...originalImplementation,                        signInUp: async function (input) {                            let resp = await originalImplementation.signInUp(input);                            if (resp.status === "OK" && resp.createdNewUser) {                                /*                                 * This is called during the signInUp API for third party login,                                 * but before calling the createNewSession function.                                 * At the start of the API, we do not know if it will result in a                                  * sign in or a sign up, so we cannot override the API function.                                 * Instead, we override the recipe function as shown here,                                 * and then set the relevant context only if it's a new user.                                 */
                                /*                                 * by default, the userContext Dict is {},                                 * we change it to {isSignUp: true}, since this is called in the                                  * sign up API, and this will tell the create_new_session function                                 * (which will be called next)                                 * to not create a new session in case input.userContext.isSignUp == true                                 */                                input.userContext.isSignUp = true;                            }                            return resp;                        },                    }                },            }        })    ]});

Then we consume that context in the createNewSession function to return an empty function in case the userContext.isSignUp is true

import SuperTokens from "supertokens-node";import ThirdParty from "supertokens-node/recipe/thirdparty";import Session from "supertokens-node/recipe/session";
SuperTokens.init({    appInfo: {        apiDomain: "...",        appName: "...",        websiteDomain: "..."    },    supertokens: {        connectionURI: "...",    },    recipeList: [        ThirdParty.init({/* See previous step... */}),        Session.init({            override: {                functions: (originalImplementation) => {                    return {                        ...originalImplementation,                        createNewSession: async function (input) {                            if (input.userContext.isSignUp) {                                /**                                 * The execution will come here only in case                                 * a sign up API is calling this function. This is because                                 * only then will the input.userContext.isSignUp === true                                 * (see above code).                                 */                                return {                                    getAccessToken: () => "",                                    getAccessTokenPayload: () => null,                                    getExpiry: async () => -1,                                    getHandle: () => "",                                    getSessionData: async () => null,                                    getTimeCreated: async () => -1,                                    getUserId: () => "",                                    revokeSession: async () => { },                                    updateAccessTokenPayload: async () => { },                                    updateSessionData: async () => { },                                    mergeIntoAccessTokenPayload: async () => { },                                    assertClaims: async () => { },                                    fetchAndSetClaim: async () => { },                                    getClaimValue: async () => undefined,                                    setClaimValue: async () => { },                                    removeClaim: async () => { },                                }; // this is an empty session. It won't result in a session being created for the user.                            }                            return originalImplementation.createNewSession(input);                        }                    }                }            }        })    ]});

As a summary, when the sign up API is called, the initial value of userContext is an empty object. We change that user context to add the isSignUp field so that that information can be communicated to the createNewSession function.

When that is called, that function checks if isSignUp === true, and if it is, it doesn't call the original implementation, and instead, just returns an empty session. This way, we don't create a session if the user is signing up, but we do create one if the user is signing in.

Default information in the user context object#

This section describes any default content added to the user context object for you to consume.


{    _default: {        /*         This is the request object that allows you to read the body / origin / headers of the API request.
        It is optional and will be defined only if the function you are overriding is called during an API.        */        request    }}


The userContext object is empty by default.

Which frontend SDK do you use?
supertokens-web-js / mobile