Repository navigation
Fix five-attempt admin login lockout and preserve invalid-password feedback - #90
Merged
SamRepository25 merged 1 commit intoSep 27, 2026
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Invalid username or password.for incorrect credentials even if failed-attempt telemetry cannot be persisted.Database deployment
This PR adds
supabase/migrations/20260927170000_five_attempt_login_lockout.sql. Ensure this migration is applied to the production Supabase project as part of deployment; the server-side lockout depends on the database RPC being available.Validation
Reviewed the application threshold, SQL threshold, lockout return fields, and existing UI countdown/blocking flow for consistency. Full build and live Supabase login tests have not been run in this environment.