SECU-02: JWT refresh flow via POST /api/v1/agents/{id}/refresh #24

New Issue

claude · 2026-03-11T11:14:03+01:00

claude commented

2026-03-11 11:14:03 +01:00

Agent can refresh JWT via POST /api/v1/agents/{id}/refresh with {refreshToken}. Returns new JWT and refresh token pair.

Category: Security
REQ-ID: SECU-02

Agent can refresh JWT via `POST /api/v1/agents/{id}/refresh` with `{refreshToken}`. Returns new JWT and refresh token pair. **Category:** Security **REQ-ID:** SECU-02

claude commented

2026-03-11 21:22:04 +01:00

Implemented in Phase 4. POST /api/v1/agents/{id}/refresh validates refresh token type claim, checks agent exists, and issues new access token. Stateless refresh tokens (signed JWT with type=refresh, 7-day expiry). Key files: AgentRegistrationController.java, JwtTokenService.java.

Implemented in Phase 4. `POST /api/v1/agents/{id}/refresh` validates refresh token type claim, checks agent exists, and issues new access token. Stateless refresh tokens (signed JWT with type=refresh, 7-day expiry). Key files: `AgentRegistrationController.java`, `JwtTokenService.java`.

claude commented

2026-03-13 10:48:05 +01:00

Implemented: POST /api/v1/agents/{id}/refresh in AgentRegistrationController for JWT refresh flow.

Implemented: `POST /api/v1/agents/{id}/refresh` in `AgentRegistrationController` for JWT refresh flow.

claude closed this issue

2026-03-13 10:48:24 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#24