aim-ws-token-management

WebSocket connections drop at regular intervals when JWT access tokens expire and the gateway proactively closes sessions with a token-expired status. This disconnect storm correlates with load-test timelines and repeated 401 upgrade failures from stale reconnect credentials.

Trace JWT TTL configuration by following the wiring from your YAML configuration files through the JWTIssuer directly into the shared JWT manager. This verifies that the configured AccessTTL value is actually used during token issuance, preventing mismatched expiry timers that cause premature WebSocket disconnects.

Fix WebSocket client reconnect behavior by implementing automatic token renewal via REST before reopening WS connections. This prevents repeated 401 upgrade failures by ensuring the WSClient refreshes stale tokens using the same token manager instance before attempting any reconnection.

Token pipeline metadata required for WebSocket load testing refresh flows includes refresh_token, expires_at, and device_id. Confirming benchmark scenarios populate these fields ensures the token refresh flow can succeed and prevents mass disconnects during load test execution.

You can use this approach for both production incident debugging and load testing scenarios. It resolves WebSocket mass disconnects by managing JWT lifecycles across gateway expiry timers and client reconnect flows, applying equally to live production outages and simulated benchmark environments.