Unknown argument `stripeCustomerId` when creating customer on signup
stripeCustomerId
automatically on signup, gives me a prisma error. I found an other thread here where the issue was the schema not having stripeCustomerId
set as optional, but my schema does. Has anyone else had this issue?Warning: You did not specify an output path for your
generator in schema.prisma. This behavior is deprecated and will no longer be supported in Prisma 7.0.0.
, but then forgot to change the PrismaClient import statement from the old default path.Handling better-auth.two_factor cookie after TOTP verification and logout
Expo plugin isn't a valid plugin
import { expo } from "@better-auth/expo";
isnt compatible with the type BetterAuthPlugin.
Error:
```
Type '{ id: "expo"; init: (ctx: AuthContext) => { options: { trustedOrigins: string[]; }; }; onRequest(request: Request, ctx: AuthContext): Promise<{ request: Request; } | undefined>; hooks: { ...; }; }' is not assignable to type 'BetterAuthPlugin'....Trying to make my plugin work as npm package with bun
bun link my-plugin
bun link my-plugin
something worong with cloudfalre
Exploring Better Auth SSO Plugin – Guidance on authClient.sso.register Usage
authClient.sso.register
, especially since invoking this API requires an active user session. Additionally, there is no implementation provided for signInWithTestUser
, which added to the confusion.
Documentation reference: Better Auth SSO Plugin - Register an OIDC Provider...Multiple apps sharing the same database using Better Auth
organization plugin for "embedded" use case (no user login)
How to manage 2FA Trusted Devices?
how to use kysylo-adapter with better-auth
[OIDC] federated logout (`end_session_endpoint`)
end_session_endpoint
in the OIDC provider plugin for federated (RP-initiated) logout use cases?
Section 2 "RP-Initiated Logout" in the spec here: https://openid.net/specs/openid-connect-rpinitiated-1_0.html...Better Auth with Capacitor
Multiple accounts with the same e-mail
Magic link verify on a secondary device
Account linking extra info
allowDifferentEmails: true.
it seems like there’s no way to extend the account schema. I think it’s pretty common to have information like the name and email of a newly linked Google account, so that on the client side — when using authClient.listAccounts
— I can display each account’s name, email, or other relevant info.
I tried using the hooks and databaseHooks, but I couldn’t get it to work....plugin schema: onDelete: "cascade" does not work?
manage sessions in server
How to create headers on the server
listOrganizations
or listUsers
on the server by passing in the user.id
that I get back from the already validated token header.
I could query the DB myself, but that kinda feels off...what tables are a must for better auth to work
Is it a possible to use a relation table as type for fields in additionalFields ? (beginner 😅)
pages
field of the user directly from the session (code snippet below). (It's another table).
Is it possible / a good idea to include this kind of data directly in the session (via customSession) or should I rather fetch it separately using a /me
endpoint after login?
I’m not an auth expert, so I’m not 100% sure what the best practice is here – any feedback or guidance would be super appreciated! 🙏...