What the developer wrote
Authored by Nicolas Dorier
fix test
What changed, and why it matters
This is a one-line change to a test file. It updates a test case that checks for a duplicate email error so that it also provides a current password. The change does not modify any production code and has no direct security impact on the BTCPay Server application itself.
No security action required. Review the related production code change that necessitated this test update to ensure requiring CurrentPassword for email updates is intentional and correctly implemented.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies BTCPayServer.Tests/GreenfieldAPITests.cs. A test for duplicate email validation now includes CurrentPassword = “abceudhqw” in the UpdateCurrentUser request. A subsequent test already covers invalid current password validation. This appears to be a test fix, likely because the API now requires a current password when updating the user’s email, and the test was failing without it. No application logic is changed.
Changed components
BTCPayServer.Tests/GreenfieldAPITests.csInspect captured patch +1 / −1
### BTCPayServer.Tests/GreenfieldAPITests.cs
@@ -1162,7 +1162,7 @@ await AssertValidationError(["Email"],
// Duplicate email
await AssertValidationError(["Email"],
async () => await adminClient.UpdateCurrentUser(
- new UpdateApplicationUserRequest { Email = "test@gmail.com" }));
+ new UpdateApplicationUserRequest { Email = "test@gmail.com", CurrentPassword = "abceudhqw" }));
// Invalid current password
await AssertValidationError(["CurrentPassword"],Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.