mirror of https://github.com/Memo-2023/mana-monorepo.git synced 2026-05-14 21:41:09 +02:00

Till JS 8e8b6ac65f fix(mana-auth) + chore: rewrite /api/v1/auth/login JWT mint, remove Matrix stack

This commit bundles two unrelated changes that were swept together by an
accidental `git add -A` in another working session. Documented here so the
history reflects what's actually inside.

═══════════════════════════════════════════════════════════════════════
1. fix(mana-auth): /api/v1/auth/login mints JWT via auth.handler instead
   of api.signInEmail
═══════════════════════════════════════════════════════════════════════

Previous attempt (commit 55cc75e7d) tried to fix the broken JWT mint in
/api/v1/auth/login by switching the cookie name from `mana.session_token`
to `__Secure-mana.session_token` for production. That was necessary but
not sufficient: Better Auth's session cookie value isn't just the raw
session token, it's `<token>.<HMAC>` where the HMAC is derived from the
better-auth secret. Reconstructing the cookie from auth.api.signInEmail's
JSON response only gave us the raw token, so /api/auth/token's
get-session middleware still couldn't validate it and the JWT mint kept
silently failing.

Real fix: do the sign-in via auth.handler (the HTTP path) rather than
auth.api.signInEmail (the SDK path). The handler returns a real fetch
Response with a Set-Cookie header containing the fully signed cookie
envelope. We capture that header verbatim and forward it as the cookie
on the /api/auth/token request, which now passes validation and mints
the JWT correctly.

Verified end-to-end on auth.mana.how:

  $ curl -X POST https://auth.mana.how/api/v1/auth/login \
      -d '{"email":"...","password":"..."}'
  {
    "user": {...},
    "token": "<session token>",
    "accessToken": "eyJhbGciOiJFZERTQSI...",   ← real JWT now
    "refreshToken": "<session token>"
  }

Side benefits:
- Email-not-verified path is now handled by checking
  signInResponse.status === 403 directly, no more catching APIError
  with the comment-noted async-stream footgun.
- X-Forwarded-For is forwarded explicitly so Better Auth's rate limiter
  and our security log see the real client IP.
- The leftover catch block now only handles unexpected exceptions
  (network errors etc); the FORBIDDEN-checking logic in it is dead but
  harmless and left in for defense in depth.

═══════════════════════════════════════════════════════════════════════
2. chore: remove the entire self-hosted Matrix stack (Synapse, Element,
   Manalink, mana-matrix-bot)
═══════════════════════════════════════════════════════════════════════

The Matrix subsystem ran parallel to the main Mana product without any
load-bearing integration: the unified web app never imported matrix-js-sdk,
the chat module uses mana-sync (local-first), and mana-matrix-bot's
plugins duplicated features the unified app already ships natively.
Keeping it alive cost a Synapse + Element + matrix-web + bot container
quartet, three Cloudflare routes, an OIDC provider plugin in mana-auth,
and a steady drip of devlog/dependency churn.

Removed:
- apps/matrix (Manalink web + mobile, ~150 files)
- services/mana-matrix-bot (Go bot with ~20 plugins)
- docker/matrix configs (Synapse + Element)
- synapse/element-web/matrix-web/mana-matrix-bot services in
  docker-compose.macmini.yml
- matrix.mana.how/element.mana.how/link.mana.how Cloudflare tunnel routes
- OIDC provider plugin + matrix-synapse trustedClient + matrixUserLinks
  table from mana-auth (oauth_* schema definitions also removed)
- MatrixService import path in mana-media (importFromMatrix endpoint)
- Matrix notification channel in mana-notify (worker, metrics, config,
  channel_type enum, MatrixOptions handler)
- Matrix entries from shared-branding (mana-apps + app-icons),
  notify-client, the i18n bundle, the observatory map, the credits
  app-label list, the landing footer/apps page, the prometheus + alerts
  + promtail tier mappings, and the matrix-related deploy paths in
  cd-macmini.yml + ci.yml

Devlog/manascore/blueprint entries that mention Matrix are left intact
as historical record. The oauth_* + matrix_user_links Postgres tables
stay on existing prod databases — code can no longer write to them, drop
them in a follow-up migration if you want them gone for real.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-08 16:32:13 +02:00

2.4 KiB

Raw Permalink Blame History

mana-notify (Go)

Go replacement for the NestJS mana-notify service. Unified notification microservice for email, push, and webhook notifications.

Architecture

Language: Go 1.25
Database: PostgreSQL (pgx v5, 5 tables in notify schema)
Queue: Go channels + goroutine worker pool (replaces BullMQ)
Metrics: Prometheus
Port: 3040

Endpoints

Notifications (X-Service-Key auth)

POST /api/v1/notifications/send — Send immediately
POST /api/v1/notifications/schedule — Schedule for future
POST /api/v1/notifications/batch — Batch send (max 100)
GET /api/v1/notifications/{id} — Get status
DELETE /api/v1/notifications/{id} — Cancel pending

Templates (X-Service-Key auth)

GET /api/v1/templates — List all
GET /api/v1/templates/{slug} — Get by slug
POST /api/v1/templates — Create
PUT /api/v1/templates/{slug} — Update
DELETE /api/v1/templates/{slug} — Delete
POST /api/v1/templates/{slug}/preview — Preview
POST /api/v1/templates/preview — Preview custom

Devices (JWT auth)

POST /api/v1/devices/register — Register push device
GET /api/v1/devices — List devices
DELETE /api/v1/devices/{id} — Unregister

Preferences (JWT auth)

GET /api/v1/preferences — Get preferences
PUT /api/v1/preferences — Update preferences

System

GET /health — Health check
GET /metrics — Prometheus metrics

Notification Channels

Channel	Service	Worker Concurrency	Max Retries
Email	Stalwart SMTP (self-hosted, see `docs/MAIL_SERVER.md`)	5	3
Push	Expo Push API	10	3
Webhook	HTTP callback	10	5

Commands

go run ./cmd/server          # Dev
go build -o bin/mana-notify ./cmd/server  # Build
go test ./...                # Test

Environment Variables

Variable	Default	Description
`PORT`	3040	Server port
`DATABASE_URL`	postgresql://...localhost:5432/mana_notify	PostgreSQL
`SERVICE_KEY`	dev-service-key	Service-to-service auth
`MANA_AUTH_URL`	http://localhost:3001	JWT validation
`SMTP_HOST`	stalwart	SMTP host (self-hosted Stalwart)
`SMTP_PORT`	587	SMTP port
`SMTP_USER`		SMTP username
`SMTP_PASSWORD`		SMTP password
`SMTP_FROM`	Mana noreply@mana.how	Default from
`EXPO_ACCESS_TOKEN`		Expo push token

2.4 KiB Raw Permalink Blame History