The Web Socket protocol is handled by the web server. Apache 2.4 which is supported by SiteMinder supports this (mod_proxy_wstunnel - Apache HTTP Server Version 2.4).
Are you saying having the agent installed would prevent from the WebSocket to be initiated by the Web Server? I would be surprised if that was the case.
Or you mean to say that there are no features in SiteMinder that particularly address WebSocket? I expected this but I hoped there would be something we can do, for example terminate the WebSocket if associated SiteMinder session is no longer valid.
Thanks for any comments!