Service Documentation
auth
Login, sessions and project selection — the platform's identity source.
At a glance
| Package | @csa/auth |
| Port | 4360 |
| Framework | plain node:http (not federated) |
| Data | MongoDB (users, sessions) |
Responsibilities
- Login & sessions — create and read sessions; the studio stores the session
in the
csa_sessioncookie. - Project selection — set the active project/client for a session, which the studio injects into downstream BFF calls.
- Identity source of truth —
GET /sessions/currentis what the studio's proxy layer trusts when stamping project/client/role headers.
Interface
REST over JSON (see Auth REST):
POST /sessions— create a sessionGET /sessions/current— current sessionPOST /sessions/current/project— select active project
Why it's separate
Auth is intentionally not a GraphQL subgraph. It sits beside the federation, so session resolution is a simple, synchronous REST call the studio server makes before any proxied data request.