Hi, I have supertokens setup on my api to allow users to create an account, but the data is stored using my own DB... was wondering if it's possible to do the same with ThirdParty?

Can you elaborate? If you are using the self hosted version, ALL info generated by supertokens is stored in your db.

That is correct, but when attempting to use ThirdParty, it doesn't create data within my DB

Which thirdparty provider?

Google

So it would create the info in thirdparty_users table

It provides me with the session

Yes.

when I mean my own DB, I don't mean Supertokens db

Hmm.

I believe the question is: is there a way to easily allow the ThirdParty recipe to add the user details to a application DB, without having to write a lengthy override

^^

Ah i see. Well. You have to use the override functions to do it.

I'm working with @User and IMO, at this point it would be easier for him to create his own Oauth flow to authenticate users, and use the Sessions management he's already set up

Ah. Why is using the override function difficult? If you describe your use case and which language, I can give you the code snippet for it

Using NestJS typescript. He wants to be able to authorise a user with their google account, create a row for them in the app DB, and then give them a session with a custom payload depending on some business logic/user attributes from the app DB

Alright. Will send over code snippet soon

thanks

Thanks 🙏

You can save info in your own db like this and even modify the access token payload like this:

ts
ThirdParty.init({
    signInAndUpFeature: {
        providers: [...]
    },
    override: {
        apis: (oI) => {
            return {
                ...oI,
                signInUpPOST: async function (input) {
                    if (oI.signInUpPOST === undefined) {
                        throw Error("Should never come here")
                    }
                    let resp = await oI.signInUpPOST(input);
                    if (resp.status === "OK") {
                        if (resp.createdNewUser) {
                            let googleAccessToken = resp.authCodeResponse["access_token"];
                            let user = resp.user;
                            let session = resp.session;

                            // TODO: store info about the user in your own db

                            // TODO: You can modify the access token payload like this:
                            await session.updateAccessTokenPayload({
                                "someKey": "someValue"
                            })
                        }
                    }
                    return resp;
                }
            }
        }
    }
})

Cool it works! Thanks

Great!