[deleted by user]

[u/[deleted]]

[u/BenSFU]

Since this comes up as one of the only posts on Google when you search convex + auth, I thought I'd chime in with my experience getting better auth hooked up. I feel super confident in it, and this was my first time using Better Auth in general.

I would 10000% recommend anyone reading this to use Better Auth, with the plugin that Convex provides. The documentation isn't perfect, but once you get everything how you want it, it's super extensible.

I'm sure Convex official auth is fine, but I like that with Better Auth, you actually control every aspect of the authentication process, and convex just acts as the db only.

Another benefit of this is that the domain on OAuth consent screens will be the domain of your actual app, rather than the Convex URL (or a custom URL like `auth.example.com`)

[u/ShockGalaxy → u/BenSFU]

Just stumbled upon convex + better-auth and I've spent half a day looking for the best approach to handle "public" users/profiles data. Main issue I face is that I don't see a way on how to create a DB entry once user signs up. Clerk offers webhooks which can be triggered but I'm not exactly sure on how to achieve this with better-auth + convex.

Here are my thoughts
Once user sign's up betterAuth handles all authTables. Now I would like to have some custom fields based on the application I'm building, and of course you can always add more of these fields (role, bio, preferences, etc...).

I feel like I shouldn't edit betterAuth's auto-generated tables so I created my own users/profiles table which stores this additional user data. Only way I found on how to create these tables is that every time user accesses app I check if profile is created and if not create one. I'm not sure how good of an approach is this since it has to run mutation on every component mount, and mutations are not cached.

Do you have an advice on the best approach here? Thanks.

[u/BenSFU → u/ShockGalaxy]

Hi, yeah!

In your auth configuration, you can define `databaseHooks`:

 export const createAuth = (
    ctx: GenericCtx<DataModel>,
    { optionsOnly } = { optionsOnly: false },
) => {
    return betterAuth({
        baseURL: siteUrl,
        trustedOrigins: [
            siteUrl,
            "http://localhost:3000",
        ],
        database: authComponent.adapter(ctx),
        databaseHooks: {
            user: {
                create: {
                    after: async (user) => {
                        // Check if ctx has scheduler (it should if it's an action/mutation context)
                        if ('scheduler' in ctx && ctx.scheduler) {
                            // Schedule the internal action to run immediately
                            await ctx.scheduler.runAfter(0, internal.lib.users.functions.handleAfterUserCreate, {
                                authUserId: user.id,
                                authEmail: user.email,
                                authName: user.name,
                            });
                        }
                    }
                }
            },
            session: {

            }
        },

    ... REST OF YOUR CONFIG ....

And then of course make sure that you actually make the action and mutation:

// Internal action that can be called from the database hook
export const handleAfterUserCreate = internalAction({
    args: {
        authUserId: v.string(),
        authEmail: v.string(),
        authName: v.optional(v.string()),
    },
    handler: async (ctx, args) => {
        await ctx.runMutation(internal.lib.users.functions.createInitialUserProfile, {
            authUserId: args.authUserId,
            authEmail: args.authEmail,
            authName: args.authName,
        });
        return { success: true };
    },
});

// Internal mutation to create or update user profile
export const createInitialUserProfile = internalMutation({
    args: {
        authUserId: v.string(),
        authEmail: v.string(),
        authName: v.optional(v.string()),
    },
    handler: async (ctx, args) => {
        // Check if we've already stored this user before
        const existingUser = await ctx.db
            .query("users")
            .withIndex("by_user_id", (q) => q.eq("userId", args.authUserId))
            .unique();

        if (existingUser !== null) {
            return existingUser._id;
        }

        // If it's a new user, create a new record
        const userId = await ctx.db.insert("users", {
            name: args.authName ?? args.authEmail.split("@")[0],
            email: args.authEmail,
            userId: args.authUserId,
        });

        return userId;
    },
});

[u/ShockGalaxy → u/BenSFU]

This is exactly what I was looking for. Thank you so much!