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

[GH-ISSUE #1884] API Key Plugin: Error reading model from schema #8961

New Issue
Closed
opened 2026-04-13 04:12:31 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-13 04:12:31 -05:00
Owner
Copy Link

Originally created by @ismael-iskauskas on GitHub (Mar 19, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1884

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

If you change the plugin schema to anything different from apikey the kysely adapter can not find the schema.

the reason for this is:
the schema is defined with the key apikey in file packages/better-auth/src/plugins/api-key/schema.ts

export const apiKeySchema = ({
  timeWindow,
  rateLimitMax,
}: { timeWindow: number; rateLimitMax: number }) =>
  ({
    apikey: {
      modelName: "apikey",
      fields: {
....

but it is in the endpoints it is used with schema.apikey.modelName
example:

packages/better-auth/src/plugins/api-key/routes/create-api-key.ts line 281 to 284

const apiKey = await ctx.context.adapter.create<ApiKey>({
  model: schema.apikey.modelName,
  data: data,
});

Current vs. Expected behavior

it should work that you can change the modelName in schema of ApiKey plugin.

the fix could be easy implemented if done like in twoFactor plugin

What version of Better Auth are you using?

1.2.4

Provide environment information

Does not matter in this context

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

Client, Other

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
plugins: [
      openAPI({}),
      admin(),
      apiKey({
        schema: {
          apikey: {
            modelName: 'auth.api_keys',
            fields: {

            },
          },
        },
      }),
      twoFactor({
        schema: {
          twoFactor: {
            modelName: 'auth.two_factors',
            fields: {},
          },
        },
      }),
    ],
});

Additional context

No response

Originally created by @ismael-iskauskas on GitHub (Mar 19, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1884 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce If you change the plugin schema to anything different from apikey the kysely adapter can not find the schema. the reason for this is: the schema is defined with the key apikey in file packages/better-auth/src/plugins/api-key/schema.ts ``` ts export const apiKeySchema = ({ timeWindow, rateLimitMax, }: { timeWindow: number; rateLimitMax: number }) => ({ apikey: { modelName: "apikey", fields: { .... ``` but it is in the endpoints it is used with schema.apikey.modelName example: packages/better-auth/src/plugins/api-key/routes/create-api-key.ts line 281 to 284 ``` ts const apiKey = await ctx.context.adapter.create<ApiKey>({ model: schema.apikey.modelName, data: data, }); ``` ### Current vs. Expected behavior it should work that you can change the modelName in schema of ApiKey plugin. the fix could be easy implemented if done like in twoFactor plugin ### What version of Better Auth are you using? 1.2.4 ### Provide environment information ```bash Does not matter in this context ``` ### Which area(s) are affected? (Select all that apply) Client, Other ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, plugins: [ openAPI({}), admin(), apiKey({ schema: { apikey: { modelName: 'auth.api_keys', fields: { }, }, }, }), twoFactor({ schema: { twoFactor: { modelName: 'auth.two_factors', fields: {}, }, }, }), ], }); ``` ### Additional context _No response_
GiteaMirror added the lockedbug labels 2026-04-13 04:12:31 -05:00
GiteaMirror commented 2026-04-13 04:12:33 -05:00
Author
Owner
Copy Link

@florianmartens commented on GitHub (Mar 20, 2025):

Thanks for reporting this. This affects me too.

<!-- gh-comment-id:2739982173 --> @florianmartens commented on GitHub (Mar 20, 2025): Thanks for reporting this. This affects me too.
GiteaMirror commented 2026-04-13 04:12:33 -05:00
Author
Owner
Copy Link

@ismael-iskauskas commented on GitHub (Mar 20, 2025):

Already created an pullrequest

<!-- gh-comment-id:2740196298 --> @ismael-iskauskas commented on GitHub (Mar 20, 2025): Already created an pullrequest
GiteaMirror commented 2026-04-13 04:12:33 -05:00
Author
Owner
Copy Link

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

apikey is not currently a part of the core schema to mod and customize the table name on the plugin itself

<!-- gh-comment-id:2848862051 --> @Kinfe123 commented on GitHub (May 3, 2025): `apikey` is not currently a part of the core schema to mod and customize the table name on the plugin itself
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#8961
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?