chore(monitoring): Logging logins, introduce HTTP 403 Forbidden responses when updating links #653
Conversation
This file contains 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.
Problem
The problems are twofold:
Login emails can be clearly logged when attempting to login.
HTTP 404 Not Found response is technically incorrect when a short link & user email URL object cannot be found. The better security posture is to treat it as an unauthorized attempt to modify a URL that does not belong to said user.
Solution
Log all emails when OTP verification takes place, for both success and failure cases.
Use HTTP 403 Forbidden response if a short link cannot be found by the URL management service.
Improvements: