github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-07-16 23:20:14 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Bug with admin plugin and renamed fields #1836

New Issue
Closed
opened 2026-03-13 09:07:04 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 09:07:04 -05:00
Owner
Copy Link

Originally created by @maelp on GitHub (Sep 3, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I'm using the admin plugin, which adds a "role" field, I wanted to rename it "better_auth_role", so in the BetterAuth conf I did eg

user: {
modelName: "usersTable",
fields: {
emailVerified: "email_verified",
createdAt: "created_at",
updatedAt: "updated_at",
role: "better_auth_role", // admin plugin
banReason: "ban_reason", // admin plugin
banExpires: "ban_expires", // admin plugin
},
...
but when trying to create a user with auth.api.createUser it complains
The field "role" does not exist in the "usersTable" schema. Please update your drizzle schema or re-generate using "npx @better-auth/cli generate
so it correctly saw that I renamed my table to usersTable (also it works for the other fields like emailVerified, etc) but it seems the admin plugin fields are not translated?

Current vs. Expected behavior

It should use the renamed fields from the config

What version of Better Auth are you using?

latest

System info

latest

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

No response

Originally created by @maelp on GitHub (Sep 3, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I'm using the admin plugin, which adds a "role" field, I wanted to rename it "better_auth_role", so in the BetterAuth conf I did eg user: { modelName: "usersTable", fields: { emailVerified: "email_verified", createdAt: "created_at", updatedAt: "updated_at", role: "better_auth_role", // admin plugin banReason: "ban_reason", // admin plugin banExpires: "ban_expires", // admin plugin }, ... but when trying to create a user with auth.api.createUser it complains The field "role" does not exist in the "usersTable" schema. Please update your drizzle schema or re-generate using "npx @better-auth/cli generate so it correctly saw that I renamed my table to usersTable (also it works for the other fields like emailVerified, etc) but it seems the admin plugin fields are not translated? ### Current vs. Expected behavior It should use the renamed fields from the config ### What version of Better Auth are you using? latest ### System info ```bash latest ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_
GiteaMirror added the help wantedplugin labels 2026-03-13 09:07:04 -05:00
GiteaMirror commented 2026-03-13 09:07:06 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 3, 2025):

This is a known limitation: the admin plugin currently does not fully respect field mappings for renamed fields like role. While your config correctly maps role to better_auth_role, the plugin accesses fields by their logical names, which causes the error when the schema only has the renamed column. Other fields work because the core logic handles mapping, but the admin plugin needs to be updated to use the mapping everywhere it accesses user fields.

As a workaround, you can keep the original field name (role) in your schema, but this defeats the purpose of renaming. If you want to keep using renamed fields, you'll need to ensure both the logical and mapped names exist in your schema, or wait for a future update where the admin plugin fully supports field mapping for all plugin-added fields. This issue has been discussed and is being addressed in ongoing plugin and schema generation work (example).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 3, 2025): <!-- Answer --> This is a known limitation: the admin plugin currently does not fully respect field mappings for renamed fields like `role`. While your config correctly maps `role` to `better_auth_role`, the plugin accesses fields by their logical names, which causes the error when the schema only has the renamed column. Other fields work because the core logic handles mapping, but the admin plugin needs to be updated to use the mapping everywhere it accesses user fields. As a workaround, you can keep the original field name (`role`) in your schema, but this defeats the purpose of renaming. If you want to keep using renamed fields, you'll need to ensure both the logical and mapped names exist in your schema, or wait for a future update where the admin plugin fully supports field mapping for all plugin-added fields. This issue has been discussed and is being addressed in ongoing plugin and schema generation work ([example](https://github.com/better-auth/better-auth/pull/3021)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ea4cc79b-0117-48e0-9685-6c361f6409a7?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![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/4408)
GiteaMirror commented 2026-03-13 09:07:07 -05:00
Author
Owner
Copy Link

@maelp commented on GitHub (Sep 3, 2025):

the error seems to come from here 8466bfe2e4/packages/better-auth/src/adapters/drizzle-adapter/drizzle-adapter.ts (L245)

@maelp commented on GitHub (Sep 3, 2025): the error seems to come from here https://github.com/better-auth/better-auth/blob/8466bfe2e499f4e594c272ee42b4d6d8bd424147/packages/better-auth/src/adapters/drizzle-adapter/drizzle-adapter.ts#L245
GiteaMirror commented 2026-03-13 09:07:07 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Sep 5, 2025):

@maelp I'm going to close this as I assume we solved your issue in the Discord server

@ping-maxwell commented on GitHub (Sep 5, 2025): @maelp I'm going to close this as I assume we solved your issue in the Discord server
GiteaMirror commented 2026-03-13 09:07:08 -05:00
Author
Owner
Copy Link

@maelp commented on GitHub (Sep 5, 2025):

yes all good! perhaps you should add to the doc in either admin plugin, or the general doc mentioning the global schema, that the plugins have to use their own "local schemas" rather than the global one

@maelp commented on GitHub (Sep 5, 2025): yes all good! perhaps you should add to the doc in either admin plugin, or the general doc mentioning the global schema, that the plugins have to use their own "local schemas" rather than the global one
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label help wanted plugin
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#1836
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?