Not requiring captcha for social signins
Is there any way to just not require it for social signins?
12 Replies
bump?
are you using the captcha plugin?
if so you can pass
endpoints
yes
well, but the social sign in button is on the same page as the email signin
but that's on the client. The server only requires it for paths specefied in the plugin config . For exmaple, for email and password only you can pass
endpoints: ["/sign-in/email"]
oh so its for api endpoints and not actual pages? or do i not understand
well it still forces me to complete the captcha after clicking on sign in with google

Same problem for me
Could you send me your auth config?
https://github.com/better-auth/better-auth/pull/2065
@bekacru here is my config
import { betterAuth } from 'better-auth'
import Database from 'better-sqlite3'
import { twoFactor, emailOTP, captcha } from 'better-auth/plugins'
export const auth = betterAuth({
advanced: {
cookiePrefix: 'bn',
},
database: new Database('./sqlite.db'),
emailAndPassword: {
enabled: true,
},
emailVerification: {
autoSignInAfterVerification: true,
sendOnSignUp: true,
requireEmailVerification: true,
},
socialProviders: {
google: {
clientId: process.env.BETTER_AUTH_GOOGLE_ID as string,
clientSecret: process.env.BETTER_AUTH_GOOGLE_SECRET as string,
},
apple: {
clientId: process.env.BETTER_AUTH_APPLE_ID as string,
clientSecret: process.env.BETTER_AUTH_APPLE_SECRET as string,
appBundleIdentifier: process.env.BETTER_AUTH_APPLE_APP_BUNDLE_IDENTIFIER,
},
facebook: {
clientId: process.env.BETTER_AUTH_FACEBOOK_ID as string,
clientSecret: process.env.BETTER_AUTH_FACEBOOK_SECRET as string,
},
tiktok: {
clientId: process.env.BETTER_AUTH_TIKTOK_ID as string,
clientSecret: process.env.BETTER_AUTH_TIKTOK_SECRET as string,
clientKey: process.env.BETTER_AUTH_TIKTOK_CLIENT_KEY,
},
},
plugins: [
twoFactor(),
emailOTP({
async sendVerificationOTP() {},
}),
captcha({
provider: 'cloudflare-turnstile',
secretKey: process.env.TURNSTILE_SECRET_KEY!,
endpoints: [],
}),
],
})
this is mine
@Lionel if you manage to find a solution, i will gladly take it
i have already created a pull request that solve the issue. We need better-auth team to check it https://github.com/better-auth/better-auth/pull/2065
@bekacru @admin need help please
Okay this is great