From e611894b5530e3826cf117e7d142ada44fead995 Mon Sep 17 00:00:00 2001 From: hailin Date: Thu, 15 Jan 2026 17:54:28 -0800 Subject: [PATCH] fix(trading-service): use payload.sub as accountSequence in JWT guard auth-service puts accountSequence in payload.sub, not payload.accountSequence. This mismatch caused 401 errors when accessing trading endpoints. Co-Authored-By: Claude Opus 4.5 --- .../trading-service/src/shared/guards/jwt-auth.guard.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/services/trading-service/src/shared/guards/jwt-auth.guard.ts b/backend/services/trading-service/src/shared/guards/jwt-auth.guard.ts index 176c93da..cb3a6a50 100644 --- a/backend/services/trading-service/src/shared/guards/jwt-auth.guard.ts +++ b/backend/services/trading-service/src/shared/guards/jwt-auth.guard.ts @@ -24,7 +24,7 @@ export class JwtAuthGuard implements CanActivate { try { const secret = this.configService.get('JWT_SECRET', 'default-secret'); const payload = jwt.verify(token, secret) as any; - request.user = { userId: payload.sub, accountSequence: payload.accountSequence }; + request.user = { accountSequence: payload.sub }; return true; } catch { throw new UnauthorizedException('Invalid token');