Skip to content

Set admin login lockout to five failed attempts - #91

Merged
SamRepository25 merged 3 commits into
mainfrom
fix/invalid-login-message-when-lockout-rpc-fails
Sep 27, 2026
Merged

SamRepository25 merged 3 commits into
mainfrom
fix/invalid-login-message-when-lockout-rpc-fails

Conversation

@SamRepository25

Copy link
Copy Markdown
Owner

Summary

  • Set the application threshold to five failed password attempts.
  • Add a Supabase migration updating the lockout RPC and database constraint to trigger a 30-minute lock on attempt five.
  • Keep the existing server-side lockout check and UI countdown/blocking behavior.
  • Update the login flow comment to document the five-attempt threshold.

Deployment

Apply the included Supabase migration to production as part of rollout. Lockout enforcement depends on the database RPC and application code being deployed together.

Validation

Reviewed consistency between the application threshold, SQL threshold, returned locked_until, and existing login-page countdown. No build or live authentication test was run here.

@vercel

vercel Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
codeforgedev Ready Ready Preview Sep 27, 2026 11:28am UTC

@SamRepository25
SamRepository25 merged commit 5a28a4c into main Sep 27, 2026
6 checks passed

This branch was successfully deployed

1 active deployment
Preview — bc0574ac Deployed Sep 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant