Error on Signup with OTP
Issue with Session Revocation and Middleware in Next.js

Nextjs middleware not working

Expo Google login
Authentication with Express backend + Next.js frontend
https://www.better-auth.com/docs/integrations/next#for-nextjs-release-1517-and-below...
Plugin to extend organization plugin
annotations forbetterAuth and createAuthClient
nk I fuc-ked up typescript by updating it?
both betterAuth and createAuthClient throw annotations errors.
The inferred type of 'betterAuthClient' cannot be named without a reference to '@/node_modules/better-auth/dist/shared/better-auth.BAfIsot3'. This is likely not portable. A type annotation is necessary.ts(2742)...declaration
and declarationMap
to false in your tsconfig
2. if it is a library, you're probably exporting a function that needs it's return type annotated. Good thread with some solutions here: https://github.com/pnpm/pnpm/issues/6089...
Rate Limit doesn't work for /send-verification-email
auth.api.sendVerificationEmail
from server bypasses the rate limitations, it only works when request is coming from the client using authClient.sendVerificationEmail
Cannot set additionalField when calling signUp.email
referredBy
field during user registration using signUp.email
, but TypeScript is rejecting it with the following error:
"Object literal may only specify known properties, and 'referredBy' does not exist in type "
1. I've properly configured referredBy
in my auth.ts
configuration:...Importing TWO_FACTOR_ERROR_CODES – Is It Possible?
Discord auth scopes
Different frontend and backend URL with social logins
Apple authentificaiton
Next.js + elysia.js cookie session issue

Error sign up Invalid `db[getModelName(model)].create()` invocation in

2FA email login with `auth.api`: Ensure verification is completed?
auth.api.signInEmail
to sign in to a user with 2FA (TOTP) enabled, how do I ensure that the 2FA verification has been completed for that session? I can always say that after signing in, the user is redirected to the 2FA verification flow, but I don't see any immediate Better-Auth-native way of blocking the user from simply changing the URL and go to a different page again and thus avoid 2FA.
Should the result of the auth.api.verifyTOTP
perhaps be stored in the Session
table for easy look-up to ensure that the user has indeed successfully completed the verification? Or am I completely missing something here, for instance that the user shouldn't actually be logged (i.e., no Session is created) in unless they complete 2FA?
Possible quirk: I don't use the client-side authClient, I have all interactions on server-side using auth.api.{method}
and I've done all necessary migrations and TOTP enabling/disabling from user profile works as expected. I use fullstack SvelteKit with interactions via form actions....Better Auth + Hono + Nextjs ( JStack ) Cookies
Auth service for a microservice
cloudflare error