We are using access tokens with a short lifetime of ~5 minutes and passing these tokens as a connect header on the initial CONNECT message. If the websocket connection breaks after the access token is expired, it is not possible to supply a refreshed access token, the expired token is still used on the reconnnect. Of course, that reconnect fails because the old token is expired. In the linked issue, the problem was fixed by passing the client object to the beforeConnect callback, I've done the same here.
I'm facing the same issue as https://github.com/stomp-js/rx-stomp/issues/204 in the rx-stomp library:
We are using access tokens with a short lifetime of ~5 minutes and passing these tokens as a connect header on the initial CONNECT message. If the websocket connection breaks after the access token is expired, it is not possible to supply a refreshed access token, the expired token is still used on the reconnnect. Of course, that reconnect fails because the old token is expired. In the linked issue, the problem was fixed by passing the client object to the
beforeConnectcallback, I've done the same here.Feel free to comment on, or edit my changes!
Best Nikos