-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closing connections from server with specific token, if token is no longer valid #229
Comments
I don't think there's a particularly good way to do this at the moment. I'm curious as to what your use case is -- is there a case where you want someone to stop being able to use the socket while it remains open? |
The use case: Our frontend application checks every few seconds if there is a change in the state of the backend. So in the first tab we login, go to the instance console (this is put in an iframe). In a second tab we open the same application (we are already logged in). From this tab we logout. In the first tab since the application is checking whether there has been a state change in the backend, it detects that we have logged out, so it displays a login dialog, but the console still remains in background. We could delete the iframe, but would the websocket connection be still active or not? Other possibility: If we could send the token to the server to disconnect all existing connections, which use this token |
How can i close active connections if a token is no longer valid? The novnc console no longer works if i open the url with the token in a new tab, but prior to token invalidation already opened consoles are still functioning and still connected via websockets. I can close the novnc console client side, but it would be better closing the websocket connections server side.
The text was updated successfully, but these errors were encountered: