For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
Is there any guidance on how do use Secure Websockets (wss) with the WebSocket API? I'm developing a web application that uses the WebSocket API, but I can't establish a connection because you have to use 'wss' when an application is secured by HTTPS.
I viewed this question from 2017 and it mentions an SSL Accelerator, but I don't know how that fits into my development process.
You can try stunnel, as mentioned in the Quick steps to set up an encrypted connection for ADS article.
Are you connecting to ERT Cloud or to the local TREP infrastructure? The ERT Cloud is already using wss (secure) protocol. You can see its use in the example applications here.
For local deployed infrastructure, I don't think ADS provides any support for wss, in which case you will have to use a third party load-balancer etc to provide this functionality.
I'm connecting to local TREP infrastructure via ADS. So I would need a load-balancer to implement wss? And is there a reference for what type of load balancer I need to use? Apologies, I'm genuinely not familiar with the process for adding ssl to websockets
I would refer you to the ADS installation guide (section 17.2) for encrypted connection support.
The ADS itself does not support TLS-based encryption for WebSocket protocols. However, load balancing/reverse proxy software or hardware components like the Apache HTTPD or F5 Networks Load Balancer can be used to provide encrypted functionality. Encrypted WebSocket connection support for the ADS has been tested with the Apache HTTPD. Using the Apache HTTPD, the following setup was used to provide encryption and Websocket access:
The Apache HTTPD configuration uses the following modules: • mod_ssl for encryption • mod_proxy and mod_proxy_ws for WebSocket reverse proxy functionality • For more information about the Apache HTTPD, refer to https://httpd.apache.org/
Essentially this functionality is not supported by Refinitiv, and you will have to refer to the component provider for support on implementation.
Hello @jonathan.powell
Please note that once you have finished configure the encrypted connection for ADS, the application flow and JSON message formats of WebSocket API is the same as a normal connection. You just need to establish a WebSocket connection with "wss" protocol and SSL port instead of "ws" protocol.
