You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, when an access token expires, the WebSocker-Next server closes the connection.
Sometimes, it's a problem since a token life span can be very short (a few minutes) and reconnection can be expensive.
Is it possible to think of some mechanism that allows the client to refresh the token before it expires and not close the websocket connection?
Implementation ideas
Maybe a PATCH request to the same WebSocket endpoint to update the access token can be a solution?
The text was updated successfully, but these errors were encountered:
Description
At the moment, when an access token expires, the WebSocker-Next server closes the connection.
Sometimes, it's a problem since a token life span can be very short (a few minutes) and reconnection can be expensive.
Is it possible to think of some mechanism that allows the client to refresh the token before it expires and not close the websocket connection?
Implementation ideas
Maybe a PATCH request to the same WebSocket endpoint to update the access token can be a solution?
The text was updated successfully, but these errors were encountered: