fix(auth): return consistent error response for invalid login #480
Conversation
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
1 participant
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.
Description
This pull request improves the authentication error handling during login by standardizing the response for invalid credentials. When a user provides an incorrect username or password, the API now returns a clear and consistent 401 (Unauthorized) response with a generic error message.
Fixes
Fixes inconsistent error handling for invalid login attempts where no clear feedback was provided to the client.
Checklist
Notes
Returning a 401 status for invalid credentials aligns with HTTP authentication semantics and allows frontend clients to reliably display user-friendly error messages without exposing sensitive authentication details.