Matheus
70c5586595
- packages/auth: Argon2id password hashing, JWT access tokens (jose), opaque refresh tokens with rotation, generic error messages (no user-enumeration via timing or message differences) - roles/permissions/role_permissions/user_roles/sessions/audit_logs schema (agente.md secoes 142-150); RBAC scope PLATFORM vs TENANT - withUserContext(): narrow RLS exception so a user can discover their own tenant_memberships before a tenant is chosen (login flow) - userHasPermission()/isPlatformUser(): explicit service-layer RBAC checks (roles/permissions tables are not RLS-protected — documented why in docs/AUTHENTICATION.md) - seed: permission catalog, 4 system roles, initial Platform Super Admin (password written once to FIRST_LOGIN.txt, 600, outside Git) - automated end-to-end test: login, RBAC check, refresh rotation, logout
3.0 KiB
3.0 KiB
TODO — B2BCall
PHASE 01 — Infrastructure
- Diagnóstico do servidor (Debian 13, 2 vCPU, ~1.9GB RAM, 26GB disco livre)
- Docker + Docker Compose instalados
- Estrutura de monorepo criada (apps/, packages/, infrastructure/, scripts/, docs/)
- PostgreSQL 18 (docker-compose, porta 127.0.0.1:5432)
- Redis 7 (docker-compose, porta 127.0.0.1:6379)
- Secrets gerados em
.env(POSTGRES_PASSWORD, REDIS_PASSWORD, JWT_SECRET, JWT_REFRESH_SECRET, ENCRYPTION_KEY, ESL_PASSWORD) FREESWITCH_PATconfigurado em.env(não commitado)- FreeSWITCH (build/imagem própria, ver risco de RAM abaixo)
- nginx (reverse proxy)
PHASE 02 — SaaS Core
- Monorepo Node.js/TypeScript (pnpm workspaces, tsconfig base)
- Node 22 LTS + pnpm instalados no host
packages/database(Prisma 7 + driver adapterpg, migration inicial)packages/types(TenantStatus, AgentState),packages/shared- Tabela
tenantscriada via migration (seção 29 do agente.md)
PHASE 03 — Tenant Isolation
- Tabelas
users+tenant_memberships(tenant-scoped) - RLS (
ENABLE/FORCE ROW LEVEL SECURITY+ policy) emtenant_memberships - Tenant context via
set_config('app.current_tenant_id', ..., true)(transaction-local) - Helper
withTenantContext()empackages/database - Role de banco separado para runtime (
b2bcall_app, sem SUPERUSER/BYPASSRLS) — achado crítico: o role padrão do Docker Postgres é SUPERUSER e SEMPRE ignora RLS, até com FORCE. Verdocs/TENANT_ISOLATION.md. - Teste automatizado de isolamento (
pnpm --filter @b2bcall/database run test:isolation)
PHASE 04 — Authentication / RBAC
packages/auth: hash Argon2id (@node-rs/argon2), JWT access token (jose), refresh token opaco com rotation- Tabelas
roles,permissions,role_permissions,user_roles,sessions,audit_logs login()/refreshSession()/logout()/listUserTenants()/setActiveTenant()userHasPermission()(RBAC com scope PLATFORM/TENANT)- Seed: catálogo de permissions + roles de sistema + Platform Super Admin inicial
(senha em
FIRST_LOGIN.txt, fora do Git,mustChangePassword=true) - Teste automatizado (
pnpm --filter @b2bcall/auth run test:auth) - Camada HTTP (endpoints, rate limit por IP, guards) — depende de
apps/apiexistir, ver docs/AUTHENTICATION.md → "O que falta" - Password reset por e-mail — depende de SMTP configurado
PHASE 05+ — ver agente.md seções 15 em diante (FreeSWITCH, Telefonia, Call Center,
Predictive Dialer, Recordings, AI, Billing, Frontend, Reports, Security, Tests)
Riscos conhecidos
- RAM da VM (1.9GB total): insuficiente para rodar toda a stack (Postgres + Redis + FreeSWITCH + múltiplos workers Node + Next.js) simultaneamente sem swap/OOM. Avaliar upgrade de RAM antes de subir FreeSWITCH + frontend + workers juntos.
- Disco (26GB livre): build do FreeSWITCH + imagens Docker + gravações vão consumir
espaço rápido. Monitorar com
df -h.