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
When working with subscriptions it would be useful to configure handshake interceptors like HttpSessionHandshakeInterceptor or other custom interceptors.
As for now, the only way I found of doing so was to opt-out of the whole websocket autoconfiguration. However, this could be achieved with a small change in the WebsocketAutoconfiguration class.
I did a very simple implementation that would perfectly work out for me, you can see it in this commit. Basically, I added a HandshakeInterceptorsFactory interface that can be implemented, if needed, to register interceptors.
I think this would be a good enhancement to the websocket autoconfiguration feature. Let me know your opinions.
Regards
The text was updated successfully, but these errors were encountered:
I am trying to secure web socket requests by introspecting the authorization header sent on the connection_init request and then populate the DefaultGlobalContext with the user session info.
Hi!
When working with subscriptions it would be useful to configure handshake interceptors like
HttpSessionHandshakeInterceptor
or other custom interceptors.As for now, the only way I found of doing so was to opt-out of the whole websocket autoconfiguration. However, this could be achieved with a small change in the
WebsocketAutoconfiguration
class.I did a very simple implementation that would perfectly work out for me, you can see it in this commit. Basically, I added a
HandshakeInterceptorsFactory
interface that can be implemented, if needed, to register interceptors.I think this would be a good enhancement to the websocket autoconfiguration feature. Let me know your opinions.
Regards
The text was updated successfully, but these errors were encountered: