[GH-ISSUE #3556] Incorrect FK reference for the teamMember table #9644

New Issue

GiteaMirror · 2026-04-13T05:14:19-05:00

GiteaMirror commented

2026-04-13 05:14:19 -05:00

Originally created by @max-om on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3556

Hi, with teams in organization plugin, shouldn't the teamMember have a FK reference to the memberId instead of the userId ? Logically, a user can belong to multiple organizations. But a member (org id + user id) can only belong to one org. So if a member is deleted then they should also be deleted in the teamMember table.

With the current implementation when a member is deleted, the team member is not deleted. The team member only gets deleted if the user is deleted which does not sound right logically.

Can we modify the references of default schema fields using the additional fields option or is there a way to customise the field to add references ? Currently, it looks like customising a schema feature only allows to change the name of the field and does not allow us to do anything else like what is allowed in createFieldAttribute

Originally created by @max-om on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3556 Hi, with teams in organization plugin, shouldn't the teamMember have a FK reference to the memberId instead of the userId ? Logically, a user can belong to multiple organizations. But a member (org id + user id) can only belong to one org. So if a member is deleted then they should also be deleted in the teamMember table. With the current implementation when a member is deleted, the team member is not deleted. The team member only gets deleted if the user is deleted which does not sound right logically. Can we modify the references of default schema fields using the additional fields option or is there a way to customise the field to add references ? Currently, it looks like customising a schema feature only allows to change the name of the field and does not allow us to do anything else like what is allowed in createFieldAttribute

GiteaMirror added the locked label 2026-04-13 05:14:19 -05:00

GiteaMirror closed this issue

2026-04-13 05:14:20 -05:00

GiteaMirror commented

2026-04-13 05:14:21 -05:00

@dosubot[bot] commented on GitHub (Jul 23, 2025):

You're correct—the current teamMember table in the organization plugin uses a foreign key to userId, not memberId, which means deleting a member does not cascade to teamMember records. This can leave orphaned teamMember entries if a user remains active elsewhere. The schema customization options (like additionalFields or fields) only let you change field names or add extra fields, not alter the core foreign key structure or relationships. There isn't a built-in or documented way to change the FK reference in teamMember to memberId using the current plugin configuration options—doing so would require deeper changes at the schema and adapter level, which aren't officially supported right now citation citation.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 23, 2025):  You're correct—the current teamMember table in the organization plugin uses a foreign key to userId, not memberId, which means deleting a member does not cascade to teamMember records. This can leave orphaned teamMember entries if a user remains active elsewhere. The schema customization options (like additionalFields or fields) only let you change field names or add extra fields, not alter the core foreign key structure or relationships. There isn't a built-in or documented way to change the FK reference in teamMember to memberId using the current plugin configuration options—doing so would require deeper changes at the schema and adapter level, which aren't officially supported right now [citation](https://github.com/better-auth/better-auth/blob/602ab7c4c6913d601994de0ae679be6645a58d69/packages/better-auth/src/plugins/organization/schema.ts) [citation](https://github.com/better-auth/better-auth/blob/602ab7c4c6913d601994de0ae679be6645a58d69/packages/better-auth/src/plugins/organization/adapter.ts).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d2c61fb5-2a36-4503-80db-4bdc7f091d90?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3556)

GiteaMirror commented

2026-04-13 05:14:22 -05:00

@max-om commented on GitHub (Jul 23, 2025):

@dosu how can I solve this issue ?

@max-om commented on GitHub (Jul 23, 2025): @dosu how can I solve this issue ?

GiteaMirror commented

2026-04-13 05:14:23 -05:00

@dosubot[bot] commented on GitHub (Jul 23, 2025):

This isn't supported out-of-the-box: the organization plugin's schema and adapter logic are tightly coupled to userId as the foreign key in teamMember, and schema customization options only let you rename fields or add extras—not change relationships or cascade rules (schema.ts, organization.ts).

If you need cascading deletes when a member is removed, you have a few options:

Implement manual cascading in your adapter logic: when deleting a member, also delete all teamMember records for that member's userId and organizationId. This is the most maintainable workaround and doesn't require forking the plugin (adapter.ts).
Use database-level triggers or constraints to enforce cascading deletes from member to teamMember, but this requires careful setup and maintenance outside of Better Auth.
Fork and modify the plugin to use memberId as the FK in teamMember, but this is fragile and will make upgrades harder.

If you go with a workaround, keep your custom logic isolated and document it well so you can adapt to future upstream changes.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 23, 2025):  This isn't supported out-of-the-box: the organization plugin's schema and adapter logic are tightly coupled to userId as the foreign key in teamMember, and schema customization options only let you rename fields or add extras—not change relationships or cascade rules ([schema.ts](https://github.com/better-auth/better-auth/blob/602ab7c4c6913d601994de0ae679be6645a58d69/packages/better-auth/src/plugins/organization/schema.ts), [organization.ts](https://github.com/better-auth/better-auth/blob/602ab7c4c6913d601994de0ae679be6645a58d69/packages/better-auth/src/plugins/organization/organization.ts)). If you need cascading deletes when a member is removed, you have a few options: - Implement manual cascading in your adapter logic: when deleting a member, also delete all teamMember records for that member's userId and organizationId. This is the most maintainable workaround and doesn't require forking the plugin ([adapter.ts](https://github.com/better-auth/better-auth/blob/602ab7c4c6913d601994de0ae679be6645a58d69/packages/better-auth/src/plugins/organization/adapter.ts)). - Use database-level triggers or constraints to enforce cascading deletes from member to teamMember, but this requires careful setup and maintenance outside of Better Auth. - Fork and modify the plugin to use memberId as the FK in teamMember, but this is fragile and will make upgrades harder. If you go with a workaround, keep your custom logic isolated and document it well so you can adapt to future upstream changes.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ebfcd366-39ba-4bc6-93d6-68708ff9c56a?feedback_type=other)  [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3556)

GiteaMirror commented

2026-04-13 05:14:24 -05:00

@Kinfe123 commented on GitHub (Aug 11, 2025):

it is already fixed. closing this.

@Kinfe123 commented on GitHub (Aug 11, 2025): it is already fixed. closing this.

GiteaMirror commented

2026-04-13 05:14:25 -05:00

@max-om commented on GitHub (Aug 11, 2025):

Hi @Kinfe123, this issue is not fixed.

Changes in release v1.3.5-beta.5, only adds support to referencing teamId in the team members table.

The issue here is referencing member id from the members table in the team members table instead of userId (or add additional column for member id reference).

With the proposed changes, if a member is deleted from an org, but a user still exists, the member record will be deleted from the members table but the team member record for the deleted member will still exist as the team member table references user id and org id and there is no reference to member id.

The team member will only be deleted if a team is deleted or a user is deleted

@max-om commented on GitHub (Aug 11, 2025): Hi @Kinfe123, this issue is not fixed. Changes in release [v1.3.5-beta.5](https://github.com/better-auth/better-auth/releases/tag/v1.3.5-beta.5), only adds support to referencing teamId in the team members table. - https://github.com/better-auth/better-auth/pull/3801/files - https://github.com/better-auth/better-auth/pull/3833/files The issue here is referencing member id from the members table in the team members table instead of userId (or add additional column for member id reference). With the proposed changes, if a member is deleted from an org, but a user still exists, the member record will be deleted from the members table but the team member record for the deleted member will still exist as the team member table references user id and org id and there is no reference to member id. The team member will only be deleted if a team is deleted or a user is deleted

GiteaMirror commented

2026-04-13 05:14:25 -05:00

@max-om commented on GitHub (Aug 11, 2025):

Can you please reopen the issue as this is not fixed. Thanks @Kinfe123

@max-om commented on GitHub (Aug 11, 2025): Can you please reopen the issue as this is not fixed. Thanks @Kinfe123

GiteaMirror commented

2026-04-13 05:14:26 -05:00

@dosubot[bot] commented on GitHub (Nov 10, 2025):

Hi, @max-om. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

You raised a concern that the teamMember table should reference memberId instead of userId to enable proper cascading deletes.
Currently, deleting a member leaves orphaned teamMember entries due to this foreign key setup.
I confirmed this limitation and suggested workarounds like manual cascading deletes or database triggers.
Although the issue was closed by a maintainer stating it was fixed, you clarified that recent updates only added support for referencing teamId, not memberId.
You requested reopening the issue for a proper fix.

Next Steps:

Please confirm if this issue is still relevant with the latest version of better-auth by commenting here.
If no further activity occurs, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 10, 2025): Hi, @max-om. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You raised a concern that the `teamMember` table should reference `memberId` instead of `userId` to enable proper cascading deletes. - Currently, deleting a member leaves orphaned `teamMember` entries due to this foreign key setup. - I confirmed this limitation and suggested workarounds like manual cascading deletes or database triggers. - Although the issue was closed by a maintainer stating it was fixed, you clarified that recent updates only added support for referencing `teamId`, not `memberId`. - You requested reopening the issue for a proper fix. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of better-auth by commenting here. - If no further activity occurs, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!

GiteaMirror commented

2026-04-13 05:14:27 -05:00

@max-om commented on GitHub (Nov 17, 2025):

Hi @dosu, yes it is still relevant

@max-om commented on GitHub (Nov 17, 2025): Hi @dosu, yes it is still relevant

GiteaMirror commented

2026-04-13 05:14:28 -05:00

@max-om commented on GitHub (Nov 17, 2025):

The fix here only fixes the implementation programmatically using the better auth API but I believe this is more of a logical design of a memberId FK reference with cascade delete in the team members table: https://github.com/better-auth/better-auth/pull/5063/files

@max-om commented on GitHub (Nov 17, 2025): The fix here only fixes the implementation programmatically using the better auth API but I believe this is more of a logical design of a memberId FK reference with cascade delete in the team members table: https://github.com/better-auth/better-auth/pull/5063/files

GiteaMirror commented

2026-04-13 05:14:29 -05:00

@dosubot[bot] commented on GitHub (Nov 17, 2025):

Thanks for confirming. The issue is still unresolved: the teamMember table continues to use userId as its foreign key, not memberId, and this isn't configurable through current schema customization options. Recent changes (like v1.3.5-beta.5 and related PRs) only added or fixed the teamId reference, not the core problem of referencing memberId instead of userId. As a result, deleting a member does not cascade to teamMember records, which can leave orphaned entries if the user remains active elsewhere. There are no built-in or documented ways to change this relationship—addressing it would require manual adapter logic, database triggers, or forking the plugin, all of which come with maintenance risks and are not officially supported right now.

If you need a workaround, manual cascading deletes in your adapter logic or database-level triggers are the most practical options until deeper schema customization is supported.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Nov 17, 2025):  Thanks for confirming. The issue is still unresolved: the teamMember table continues to use userId as its foreign key, not memberId, and this isn't configurable through current schema customization options. Recent changes (like v1.3.5-beta.5 and related PRs) only added or fixed the teamId reference, not the core problem of referencing memberId instead of userId. As a result, deleting a member does not cascade to teamMember records, which can leave orphaned entries if the user remains active elsewhere. There are no built-in or documented ways to change this relationship—addressing it would require manual adapter logic, database triggers, or forking the plugin, all of which come with maintenance risks and are not officially supported right now. If you need a workaround, manual cascading deletes in your adapter logic or database-level triggers are the most practical options until deeper schema customization is supported.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fc69ecbf-a32d-42cb-ad0b-5000db615298?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3556)

GiteaMirror commented

2026-04-13 05:14:30 -05:00

@max-om commented on GitHub (Nov 17, 2025):

@dosu, yes, I have implemented a custom logic at the moment...but is there an option for additional fields for the team members table similar to other tables so that we can modify schema to configure additional fields ?

@max-om commented on GitHub (Nov 17, 2025): @dosu, yes, I have implemented a custom logic at the moment...but is there an option for additional fields for the team members table similar to other tables so that we can modify schema to configure additional fields ?

GiteaMirror commented

2026-04-13 05:14:31 -05:00

@dosubot[bot] commented on GitHub (Nov 17, 2025):

No, the teamMember table does not support adding additional fields via schema customization—unlike other organization tables, it lacks an additionalFields option in the plugin configuration. You can only rename existing fields for teamMember, not add new ones through the standard config. If you need extra columns, you’d have to extend the schema manually or modify the adapter, but this isn’t officially supported and could complicate upgrades. For reference, see the schema config structure and limitations here.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Nov 17, 2025):  No, the teamMember table does not support adding additional fields via schema customization—unlike other organization tables, it lacks an `additionalFields` option in the plugin configuration. You can only rename existing fields for teamMember, not add new ones through the standard config. If you need extra columns, you’d have to extend the schema manually or modify the adapter, but this isn’t officially supported and could complicate upgrades. For reference, see the schema config structure and limitations [here](https://github.com/better-auth/better-auth/blob/d768852258d1fea921984196806608af2983a867/packages/better-auth/src/plugins/organization/types.ts#L248-L306).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4bf9c415-3ed6-4e11-b4c0-c1c49160bd93?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3556)

Sign in to join this conversation.

Branches Tags

2026-05-22/chore/adopt-agents-md

2026-05-22/refactor/string-case-utils

dependabot/npm_and_yarn/uuid-14.0.0

dependabot/npm_and_yarn/turbo-2.9.14

changeset-release/main

main

2026-05-14/fix/passkey-verify-error-and-claim

dependabot/npm_and_yarn/samlify-2.13.0

dependabot/npm_and_yarn/ws-8.20.1

changeset-release/next

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-519ef7475f

dependabot/github_actions/github-actions-98f3470200

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

2026-05-13/ci/stabilize-docker-startup

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-07/fix/admin-set-password-upsert

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

2026-04-21/fix/oauth-rfc-input-validation

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

claude/slack-update-stripe-docs-consistency-8Sc0w

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-24/fix/update-user-info-on-link

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#9644