Skip to content

fix: configurable lockout threshold via config.toml to prevent lockout loop #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 1 commit into from
May 23, 2026
+10 −0
Merged

fix: configurable lockout threshold via config.toml to prevent lockout loop #414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions sites/sh1pt.com/supabase/config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -412,3 +412,13 @@ s3_region = "env(S3_REGION)"
s3_access_key = "env(S3_ACCESS_KEY)"
# Configures AWS_SECRET_ACCESS_KEY for S3 bucket
s3_secret_key = "env(S3_SECRET_KEY)"

# Configure brute-force lockout protection. Without explicit settings,
# Supabase GoTrue uses aggressive exponential backoff defaults that
# can lock users out for 5+ hours after repeated failed sign-in attempts.
[auth.security]
# Maximum failed login attempts before lockout kicks in.
max_failed_login_attempts = 10
# Duration of the lockout after exceeding max failed attempts.
lockout_duration = "15m"

Loading