Architecture: Where should password reset live — per-app or shared library...

Documentation for Sessions

🏗️ Architecture: Where should password reset live — per-app or shared library...

Date: 2026-03-27
Time: 18:02:43 UTC
Session: gspace1-280.4
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Where should password reset live — per-app or shared library?

Task: Not specified

🎯 Decision Made

Chosen:

Backend: endpoints in BackendAuthController (same as login/register). Frontend: AuthService methods + shared components in @auth-core. Reusable across all 6 Angular apps + Tauri + Capacitor automatically.

Options Considered:

Per-app implementation
Shared @auth-core library (chosen)
New dedicated password-reset library

💭 Reasoning

Platform users already have password reset in platform-users.service.ts but GoGrab Space users (L1-L3) have NOTHING — no endpoints, no schema fields, no frontend pages. The login page 'Forgot password?' shows a JavaScript alert. The fix must follow the same shared library pattern as login: backend endpoints in backend-auth, frontend service methods in @auth-core, shared components. This ensures all apps get password reset without per-app duplication.

📁 Files Involved

APIs/backend-api/src/app/backend-auth/backend-auth.controller.ts
APIs/backend-api/src/app/backend-auth/backend-auth.service.ts
libs/libs-foundational/auth-core/src/lib/services/auth.service.ts
apps/gograb-space/src/app/auth/pages/login.page.ts

🔗 Related

Decision ID: dev_1774634562919_sw8suta
Session: 280
Workspace: gspace1

Auto-generated by MCP Smart Consolidation