github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1778] "The following field is invalid: Auth Profile > Role" after adding admin plugin #8914

New Issue
Closed
opened 2026-04-13 04:09:46 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:09:46 -05:00
Owner
Copy Link

Originally created by @jancbeck on GitHub (Mar 11, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1778

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. use neondb (postgres), next, google social provider & admin plugin
  2. add some users before enabling the admin plugin
  3. enable the admin plugin
  4. run migrations (I use kysely)
  5. attempt login via google

Current vs. Expected behavior

On attempted login with google, next logs "The following field is invalid: Auth Profile > Role" and the browser shows the BetterAuth error that forwards back to the application.

Looking at the users table I can see the "role" column has been added but it contained nothing. When I added "user" to the existing users role, the error disappeared and users can login correctly.

I'd expect the migrations to not just add the new column but also fill in the default role.

What version of Better Auth are you using?

1.2.3

Provide environment information

- OS: Vercel (??)
- Browser: latest Safari / Chrome

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

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  plugins: [expo(), admin(), openAPI()],
  database: {
    dialect: new PostgresDialect({
      pool: new Pool({
        connectionString: process.env.BETTER_AUTH_DATABASE_URI,
      }),
    }),
    type: "postgres",
  },
  emailAndPassword: {
    enabled: false,
  },
  socialProviders: {
    google: {
      clientId: String(process.env.GOOGLE_CLIENT_ID),
      clientSecret: String(process.env.GOOGLE_CLIENT_SECRET),
    },
    apple: {
      clientId: String(process.env.APPLE_CLIENT_ID),
      clientSecret: String(process.env.APPLE_CLIENT_SECRET),
    },
  },
  account: {
    accountLinking: {
      enabled: true,
    },
  },
})

Additional context

No response

Originally created by @jancbeck on GitHub (Mar 11, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1778 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. use neondb (postgres), next, google social provider & admin plugin 2. add some users before enabling the admin plugin 3. enable the admin plugin 4. run migrations (I use kysely) 5. attempt login via google ### Current vs. Expected behavior On attempted login with google, next logs "The following field is invalid: Auth Profile > Role" and the browser shows the BetterAuth error that forwards back to the application. Looking at the users table I can see the "role" column has been added but it contained nothing. When I added "user" to the existing users role, the error disappeared and users can login correctly. I'd expect the migrations to not just add the new column but also fill in the default role. ### What version of Better Auth are you using? 1.2.3 ### Provide environment information ```bash - OS: Vercel (??) - Browser: latest Safari / Chrome ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ plugins: [expo(), admin(), openAPI()], database: { dialect: new PostgresDialect({ pool: new Pool({ connectionString: process.env.BETTER_AUTH_DATABASE_URI, }), }), type: "postgres", }, emailAndPassword: { enabled: false, }, socialProviders: { google: { clientId: String(process.env.GOOGLE_CLIENT_ID), clientSecret: String(process.env.GOOGLE_CLIENT_SECRET), }, apple: { clientId: String(process.env.APPLE_CLIENT_ID), clientSecret: String(process.env.APPLE_CLIENT_SECRET), }, }, account: { accountLinking: { enabled: true, }, }, }) ``` ### Additional context _No response_
GiteaMirror added the lockedbug labels 2026-04-13 04:09:46 -05:00
GiteaMirror commented 2026-04-13 04:09:47 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 5, 2025):

is this still an issue ?

<!-- gh-comment-id:2849845041 --> @Kinfe123 commented on GitHub (May 5, 2025): is this still an issue ?
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 bug locked
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#8914
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?