🏗️ Architecture: How to fix auth/sign-in in gograb-ai app for browser users?

Date: 2026-03-02
Time: 15:55:15 UTC
Session: gspace1-166.2
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How to fix auth/sign-in in gograb-ai app for browser users?

Task: Fix auth/sign-in in gograb-ai app

🎯 Decision Made

Chosen:

Expanded desktopAuthGuard → appAuthGuard to enforce auth for ALL contexts (browser, desktop, mobile, embedded). Added /login route using shared LoginComponent from @auth-ui. Removed inline login popover. Set AUTH_LOGIN_ROUTE='/login' and AUTH_REDIRECT_STRATEGY='navigate'. Added provideApiConfig() for explicit API URL configuration.

Options Considered:

1. Create separate browser auth guard + keep desktopAuthGuard
2. Use strictAuthGuard from @auth-ui directly on all routes
3. Expand desktopAuthGuard to handle browser context too (chosen)

💭 Reasoning

The existing guard had return true for plain browser access — a security gap. Reused the proven DRY pattern from gograb-admin: thin wrapper around shared LoginComponent, strictAuthGuard equivalent in the guard, loginPageGuard on /login route. Zero shared lib changes needed — everything already existed in @auth-ui. Single guard handles all contexts with context-aware redirect (browser→/login, native→/welcome).

📁 Files Involved

• apps/gograb-ai/src/app/core/guards/desktop-auth.guard.ts
• apps/gograb-ai/src/app/pages/login/login.component.ts
• apps/gograb-ai/src/app/app.routes.ts
• apps/gograb-ai/src/app/app.config.ts
• apps/gograb-ai/src/app/app.component.ts
• apps/gograb-ai/src/app/app.component.html
• apps/gograb-ai/src/app/app.component.scss

🔗 Related

• Decision ID: dev_1772466915340_ge5y0q1
• Session: 166
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation