fix(GRO-563): Better Auth Phase 1 - Stabilize OAuth Login #264
Reference in New Issue
Block a user
Delete Branch "fix/gro-545-social-auth-v2"
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
Phase 1 of Better Auth stabilization - unblock OAuth login flow.
Changes
Testing
Definition of Done
Note
Dev social auth credentials (social-auth-sealed-secret for groombook-dev namespace) requires actual Google/GitHub OAuth app credentials. This follow-up work is tracked as a separate infra task that will be handled once credentials are available.
cc @cpfarhood
Deployed to groombook-dev
Images:
pr-264URL: https://dev.groombook.farh.net
Ready for UAT validation.
Deployed to groombook-dev
Images:
pr-264URL: https://dev.groombook.farh.net
Ready for UAT validation.
QA Review: Changes Requested
CI Status: All checks pass (Lint, Typecheck, Test, E2E Tests, Build)
Definition of Done Verification
Issues Found
Stale PRs still open: PRs #254 and #259 remain OPEN. Definition of done requires closing these with redirect to consolidated PR #264.
Dev environment missing social auth credentials: UAT and prod overlays have containing , , , . The dev overlay only has with OIDC credentials (BETTER_AUTH_SECRET, BETTER_AUTH_URL, OIDC_*), but no social auth credentials.
Required Changes
cc @cpfarhood
QA Review: Changes Requested
CI Status: All checks pass (Lint, Typecheck, Test, E2E Tests, Build)
Definition of Done Verification
Issues Found
Stale PRs still open: PRs #254 and #259 remain OPEN. Definition of done requires closing these with redirect to consolidated PR #264.
Dev environment missing social auth credentials: UAT and prod overlays have
social-auth-sealed-secret.yamlcontaining Google/GitHub OAuth credentials. The dev overlay only hasauth-sealed-secret.yamlwith OIDC credentials, but no social auth credentials.Required Changes
social-auth-sealed-secret.yamlto dev overlay with Google/GitHub OAuth credentialscc @cpfarhood
Deployed to groombook-dev
Images:
pr-264URL: https://dev.groombook.farh.net
Ready for UAT validation.
QA Review: Changes Requested
CI Status: ✅ All checks passing (Lint, Typecheck, Test, E2E, Build, Deploy to dev)
Acceptance Criteria Review:
Issue: PR #259 is still OPEN. Per the issue spec: "Stale PRs closed with redirect to the consolidated PR" — PR #259 (fix/gro-545-social-providers-config) should be closed since PR #264 is the consolidated fix.
Action Required: Close PR #259 and redirect to PR #264 before this can be approved.
QA Approval ✅
All acceptance criteria verified against PR #264 ():
Dev credential follow-up is tracked separately per PR note.
QA Recommends: APPROVE
Security Review ✅
Issue: GRO-563 — Better Auth Phase 1: Stabilize OAuth Login
Reviewed PR #264 code against security checklist. No findings.
@cpfarhood — Security gate passed. Reassigning to CEO for prod merge.