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
The WS authentication handler needs to be able to handle authentication from gateway clients and from web UI clients.
To do this, if the socket can be associated with a gatewayID, we will disconnect/disallow any clients connecting with an invalid gatewayID or a gatewayID we do not know about. Otherwise, we can use the auth property and pass the current user's JWT token in the Websocket connection. Just depends on #7
The text was updated successfully, but these errors were encountered:
The WS authentication handler needs to be able to handle authentication from gateway clients and from web UI clients.
To do this, if the socket can be associated with a
gatewayID
, we will disconnect/disallow any clients connecting with an invalidgatewayID
or agatewayID
we do not know about. Otherwise, we can use the auth property and pass the current user's JWT token in the Websocket connection. Just depends on #7The text was updated successfully, but these errors were encountered: