saqib mirandClaude Sonnet 5
8d5731340d
Implements tasks T001-T020 from specs/002-saas-integration/tasks.md (Setup, Foundational, and User Story 1 - the P1 MVP: every inbound request is authenticated and trusted before anything happens). User Story 2 (admin onboarding/rotation/revocation) and User Story 3 (rate limiting) are not yet implemented (T021-T032 remain). Schema (prisma/schema.prisma + initial migration): - Replace the placeholder Product model (leftover starter-template scaffolding: code/description/ProductStatus enum) with the real docs/06-database-schema.md shape (externalProductId, supportEnabled, status). - Add ProductIntegration (credential ref, rotation/revocation state, allowed scope, per-integration/per-user rate limits) and CustomerReference models. - Align AuditLog to docs/06's shape (actor/actorType/entityType/ entityId/reason/metadata) -- the placeholder shape had no fields to satisfy this feature's audit requirements. Auth: - HMAC-signed short-lived tokens (issue/verify) with jti-based replay defense via Redis and a bounded clock-skew tolerance. - Credential secrets are AES-256-GCM encrypted at rest (new required INTEGRATION_CREDENTIAL_ENCRYPTION_KEY env var) since no secret manager exists in this stack yet -- see research.md "Credential storage". - New product-integration-auth.plugin.ts Fastify plugin runs the validation order in contracts/inbound-request-contract.md and populates request.reqContext only on full success; every attempt (success or failure) is audit-logged without ever persisting the raw token/credential. Unregistered product and invalid credential return an identical response (FR-010). - New POST /v1/support/requests endpoint exercises the boundary end-to-end (ticket creation itself is a future feature). Also: - Fix docker-compose.test.yml's container_name collisions -- discovered while testing this change concurrently is now covered by an app-level regression test (separate commit). - Fix test:unit to scope to tests/unit only (it was running the entire tests/** glob including integration tests) -- this feature's new integration test makes real Prisma/Redis calls, unlike the prior instantiation-only checks, so the existing glob-scoping gap became actually harmful. - Update Jenkinsfile with the new required credential. Verified: full quality gate (typecheck/lint/format/architecture/ unit tests) passes; all of User Story 1's quickstart scenarios manually verified end-to-end against a live server + Postgres + Redis; the new integration test suite verified against a live database (not run as part of `npm test`, matches existing test:integration convention). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
33 lines
803 B
Bash
33 lines
803 B
Bash
NODE_ENV=development
|
|
PORT=4501
|
|
|
|
# Build
|
|
BUILD_COMMAND=npm run build:development
|
|
|
|
# Database
|
|
POSTGRES_HOST=postgres
|
|
POSTGRES_DB=support_dev
|
|
POSTGRES_USER=support_user
|
|
POSTGRES_PASSWORD=CHANGE_ME
|
|
DATABASE_URL=postgresql://support_user:CHANGE_ME@postgres:5432/support_dev
|
|
|
|
# Redis
|
|
REDIS_HOST=redis
|
|
REDIS_PORT=6379
|
|
REDIS_PASSWORD=CHANGE_ME
|
|
|
|
# Security & CORS
|
|
JWT_SECRET=CHANGE_ME_32_CHAR_MINIMUM_SECRET
|
|
JWT_ACCESS_EXPIRES=15m
|
|
JWT_REFRESH_EXPIRES=7d
|
|
|
|
# 64 hex chars (32 bytes) — generate with: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
|
|
INTEGRATION_CREDENTIAL_ENCRYPTION_KEY=CHANGE_ME_64_HEX_CHARACTERS
|
|
CORS_ORIGINS=http://localhost:3000
|
|
|
|
# AWS S3 / storage
|
|
AWS_REGION=us-east-1
|
|
AWS_S3_BUCKET=supporthub-attachments
|
|
AWS_ACCESS_KEY_ID=CHANGE_ME
|
|
AWS_SECRET_ACCESS_KEY=CHANGE_ME
|