Architecture: How should docs-angular admin auth integrate with platform a...

Documentation for Sessions

🏗️ Architecture: How should docs-angular admin auth integrate with platform a...

Date: 2026-03-14
Time: 14:32:19 UTC
Session: gspace1-219.2
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should docs-angular admin auth integrate with platform auth?

Task: Docs auth migration to backend-api

🎯 Decision Made

Chosen:

Migrate to backend-api JWT with T0/T1 role restriction

Options Considered:

Keep DOCS_ADMIN_PASS password-based auth
Migrate to backend-api JWT with T0/T1 role restriction
Hybrid: password for docs-only, JWT for platform

💭 Reasoning

Root cause: DOCS_ADMIN_PASS was single shared secret with no audit trail. backend-api already has JWT, roles (executive/developer/admin), and shared JWT_SECRET with backend-docs-api. Chosen path provides: (1) single sign-on, (2) role-based access (T0/T1 only), (3) auditability. Docs content stays accessible to any user via projectSelectedGuard + AccessService privacy. Early warning: if backend-api and backend-docs-api JWT_SECRET diverge, tokens would fail.

📁 Files Involved

apps/docs-angular/src/app/guards/docs-admin.guard.ts
APIs/backend-docs-api/src/app/admin/admin.controller.ts
apps/docs-angular/src/app/app.config.ts

🔗 Related

Decision ID: dev_1773498739714_yxgl509
Session: 219
Workspace: gspace1

Auto-generated by MCP Smart Consolidation