test(supabase): concurrency seeding accepts Storage's duplicate answer

After e2e:shell seeds the same content-addressed drawing, Storage answers HTTP 400 with statusCode 409 (KeyAlreadyExists); any other 400 still fails. Docs: M7 adds no new write path; a TOTP code replays more than once within its span.
This commit is contained in:
bchanot committed 2026-11-02 23:31:49 +01:00
1 parent dcb1a94ee4
commit f5456f330d
4 files changed
+17 -6

No files matched your search

+2 -2
View File
@@ -163,8 +163,8 @@ rehearsed at V1-2.9; the paths and gaps are reviewed in §4.2.
N+1 is accepted too (one step of skew); a session E verifying C in step N+2
is refused (422 `mfa_verification_failed`). Measured span of one code: its
own step and the next, 30 to 60 s. Consequence: a code seen over a shoulder
or relayed by a phishing page can be replayed once by another password-holding
session within that span; it does not outlive it. Configuration that ran
or relayed by a phishing page can be replayed by any session holding the
password, more than once, within that span; it does not outlive it. Configuration that ran
the measurement: the sandbox GoTrue (`scripts/db-sandbox.sh`, image
`gotrue:v2.197.0`), which sets no MFA variable, so the image defaults apply.
The CLI and DEV stacks are configured by `supabase/config.toml` `[auth.mfa]`