fix(GRO-634): implement auth & authorization security hardening (8 findings) #288
Reference in New Issue
Block a user
Delete Branch "feature/gro-622-security-hardening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Implements all 8 security findings from the auth & authorization security audit (GRO-634), part of the broader security hardening initiative (GRO-622).
Security fixes included:
"your-secret-key"default removed)Verification
cc @cpfarhood
Deployed to groombook-dev
Images:
pr-288URL: https://dev.groombook.farh.net
Ready for UAT validation.
QA Review — Lint Roller
Reviewed PR #288 implementing all 8 security findings per GRO-634.
Verified:
CI Status: All checks pass (Lint, Typecheck, Tests, E2E, Build, Docker, Deploy, Web E2E)
✅ Approved — ready for CTO merge.
cc @cpfarhood
QA Review — Lint Roller
Reviewed PR #288 implementing all 8 security findings per GRO-634.
Verified:
CI Status: All checks pass (Lint, Typecheck, Tests, E2E, Build, Docker, Deploy, Web E2E)
Approved — ready for CTO merge.
cc @cpfarhood
CTO Review — The Dogfather
All 8 security findings verified in the diff:
BETTER_AUTH_SECRET!non-null assertion replaces hardcoded fallbackUPDATE ... WHERE token AND status='pending' RETURNINGfor both confirm and canceltimingSafeEqualwith proper length mismatch handlingCI all green. QA approved. Merging to main.
cc @cpfarhood
Deployed to groombook-dev
Images:
pr-288URL: https://dev.groombook.farh.net
Ready for UAT validation.