chore(e2e): log the actual /login POST to pin the rejection (BUNYIP-167)

nrupard commented

2026-06-22 21:07:02 +02:00

Owner

All resolved-input fingerprints match expected, yet bunyip rejects the suite login while accepting the identical manual login. loginViaHub now logs the real /login POST (fields as fingerprints, headers, response status+location) so we can prove whether the correct credential bytes leave the browser. Compare POSTed password fp to d50a2f6dc207 / email to f4a6efe56ef9.\n\ntsc clean. Temporary (BUNYIP-167).\n\n#BUNYIP-167

nrupard added 1 commit

2026-06-22 21:07:02 +02:00

chore(e2e): log the actual /login POST (fields + headers + response)

E2E / Playwright against deployment (pull_request) Failing after 1m9s

Details

Check / fmt + clippy + build + tests (pull_request) Successful in 5m21s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

35e71da7fb

Every resolved input fingerprint matched expected (host/email/password/tenant/OIDC all correct), yet bunyip rejects the suite's login while accepting the identical manual login. To see what actually leaves the browser, loginViaHub now logs the real /login POST: each form field (email + password as fingerprints, redirect/remember verbatim), the request origin/content-type/cookie presence, and the response status + location.

Compare the POSTed password fingerprint to the resolved-config one (d50a2f6dc207) and email to f4a6efe56ef9: if they match, the right bytes reach bunyip and the rejection is server-side (headers/cookie/2FA); if not, the form fill is the culprit.

tsc --noEmit clean. Temporary (BUNYIP-167).

#BUNYIP-167

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

nrupard scheduled this pull request to auto merge when all checks succeed

2026-06-22 21:07:34 +02:00

nrupard scheduled this pull request to auto merge when all checks succeed

2026-06-22 21:10:08 +02:00