-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-30563] Change error response on Send Access token request #6911
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.
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
base: main
Are you sure you want to change the base?
[PM-30563] Change error response on Send Access token request #6911
Conversation
…required to protect against enumeration attacks.
test: updating tests to match new approach.
|
New Issues (1)Checkmarx found the following issues in this Pull Request
|
|
Claude finished @ike-kottlowski's task in 2m 10s —— View job Code Review: PM-30563 - Change error response on Send Access token requestStatus: Approved SummaryThis PR improves enumeration protection for the Send access email OTP flow by ensuring identical error responses regardless of whether an email address is valid. This is a well-implemented security improvement. Changes Reviewed
Security VerificationThe enumeration protection is correctly implemented:
Code Quality
VerdictNo issues found. This is a clean, focused security improvement that follows best practices for enumeration protection. Reviewed by Claude Code |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6911 +/- ##
==========================================
- Coverage 56.08% 56.06% -0.03%
==========================================
Files 1968 1969 +1
Lines 86974 87077 +103
Branches 7748 7757 +9
==========================================
+ Hits 48783 48820 +37
- Misses 36385 36448 +63
- Partials 1806 1809 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|


🎟️ Tracking
PM-30563
SDK PR: #717
Client PR: #18620
📔 Objective
To ensure that we return the same response for a valid and invalid email, while still sending the OTP to when the email is correct.
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes