Read session from Redis directly (same as /api/user-info), use forwardToApi for all service calls

Shipped: 29 மார்ச், 2026 அன்று 8:20 PM UTC
Author: kamo
Commit: 9e920c9

Root cause: the sender profile showed 'Your colleague' because the session fetch called a non-existent SecurityService endpoint. Signature was malformed because direct fetch to EmailService lacked OTK auth. Fixes: - Session: reads *** cookie → Redis directly (same as /api/user-info) - Member/org lookup: uses forwardToApi (generates fresh OTK per call) - Template fetch: uses forwardToApi through email proxy route - Email send: still goes directly to EmailService (proven working)

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free Forever View Pricing