cameleer/cameleer-server
1
0
Fork 0
Code Issues 41 Pull Requests Actions Packages Projects Releases Wiki Activity

Persist JWT signing secret across server restarts #38

New Issue
Closed
opened 2026-03-13 13:41:13 +01:00 by claude · 0 comments
claude commented 2026-03-13 13:41:13 +01:00
Owner
Copy Link

Problem

JwtServiceImpl generates a random signing secret on each server startup. This means every server restart invalidates all issued JWTs, forcing all agents to re-register and all UI users to re-login.

In an HA/LB setup with multiple server instances, each instance would have a different secret, making tokens non-portable between instances.

Proposed Change

Make the JWT signing secret configurable via environment variable (e.g. CAMELEER_JWT_SECRET). If not set, fall back to generating a random one (current behavior, suitable for dev).

For production, the secret should be stored in a K8s Secret and mounted as an env var, shared across all server replicas.

Context

Identified during UI planning. Acceptable for single-instance v1 deployments, but blocks HA/LB scenarios where the UI connects to any backend instance behind a load balancer.

## Problem `JwtServiceImpl` generates a random signing secret on each server startup. This means every server restart invalidates all issued JWTs, forcing all agents to re-register and all UI users to re-login. In an HA/LB setup with multiple server instances, each instance would have a different secret, making tokens non-portable between instances. ## Proposed Change Make the JWT signing secret configurable via environment variable (e.g. `CAMELEER_JWT_SECRET`). If not set, fall back to generating a random one (current behavior, suitable for dev). For production, the secret should be stored in a K8s Secret and mounted as an env var, shared across all server replicas. ## Context Identified during UI planning. Acceptable for single-instance v1 deployments, but blocks HA/LB scenarios where the UI connects to any backend instance behind a load balancer.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
Accessibility (a11y) improvements
 bug
Something isn't working correctly
 cleanup
Code cleanup, dead code removal, refactoring
 epic
Epic: groups related issues
 feature
New functionality
 pmf
Product-market fit: critical for first market offer
 route-diagram
Route diagram page and execution overlay
 security
Authentication, authorization, RBAC
 ui
Frontend / React UI
 ux
UX/usability improvements
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#38
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?