Add a "who am I" endpoint so an API caller can fetch their own identity/scope, akin to /firms/me.
Technical notes — The authenticated principal treasury-rest-api/…/security/VerifiedToken already carries everything needed: ownerUuid, keyType (PERSONAL/BUSINESS/GOVERNMENT), scoped accountId/firmId, and keyId (injected via @AuthenticationPrincipal). AuthController only exposes POST /rotate. Add GET /api/v1/auth/me (or /api/v1/me) returning a thin DTO over the injected VerifiedToken — no new auth plumbing.
Verified state (Planned is correct — not done): only firm-scoped endpoints exist (/firms/me, /me/accounts, /me/employees, /me/roles in FirmController). The requested generic identity endpoint — GET /api/v1/auth/me returning a thin DTO over VerifiedToken (owner/keyType/accountId/firmId) — does not exist; AuthController still only exposes POST /rotate. Genuinely open.
Code context — The authenticated principal
treasury-rest-api/…/security/VerifiedTokenalready carries everything a "who am I" response needs:ownerUuid,keyType(PERSONAL/BUSINESS/GOVERNMENT), scopedaccountId/firmId, andkeyId— injected via@AuthenticationPrincipal. ButAuthControlleronly exposesPOST /rotate.Fix: add
GET /api/v1/auth/me(or/api/v1/me) returning a thin DTO over the injectedVerifiedToken— no new auth plumbing, parallel to the existing/firms/me.