Supported Environments
The Solace JavaScript API and Solace Node.js API are compatible with many different operating systems and platforms.
Each environment that supports client connections to the event broker using Transport Layer Security (TLS) / Secure Sockets Layer (SSL) encryption is indicated. When the term TLS/SSL is used in this documentation, it refers to these forms of data encryption.
- Support for different Transport Layer Security versions vary for each API. The versions available are TLS 1.0, TLS 1.1, and TLS 1.2. The recommended version to use is the most recent version of TLS.
- Secure Socket Layer (SSL) protocol version support varies for each API. We don't recommend that you use SSL unless it's required for backwards compatibility.
Solace JavaScript API
The Solace Messaging API for JavaScript, version 10.18 supports mainstream browsers. Support includes the latest versions of modern web desktop browsers such as Google Chrome, Safari, Firefox, Edge, and Internet Explorer. Other web and mobile browsers are expected to function properly, but no formal testing has been performed.
The Solace JavaScript API has not been formally tested with any other JavaScript platforms other than Node.js (see Solace Node.js API). For example, the React Native platform has been found to have compatibility issues with the Solace JavaScript API.
JavaScript Feature and API Support
The Solace JavaScript API is compatible and integrate with common JavaScript frameworks, although framework compatibility has not been formally tested.
Some common Solace JavaScript API features are not available in all web browsers. For example, WebSocket support is not available in all versions of Internet Explorer (in this case, the Solace Messaging API for JavaScript falls back on a transport protocol that is supported by the browser in use).
Solace Node.js API
The Solace Messaging API for Node.js, version 10.18 and later, supports the latest actively maintained Node.js platform LTS release lines.
TLS Support
Transport Layer Security (TLS) provides secure connections between the Solace JavaScript API and Solace Node.js API and event brokers. The following table shows which TLS versions are supported. The recommended version to use is the most recent version of TLS.
| TLS Version | JavaScript | Node.js |
|---|---|---|
|
TLS 1.2 |
|
|
|
TLS 1.3 event broker version 10.25+ |
10.28+ |
10.18+ |
Secure Socket Layer (SSL) protocol version support varies for each API. We don't recommend that you use SSL unless it's required for backwards compatibility.
Debugging TLS 1.3 Connections
TLS 1.3 encrypts handshake messages, not just application data, and enforces perfect forward secrecy, which prevents decryption even with server private keys. These security enhancements make traditional packet capture analysis methods ineffective. To effectively debug TLS 1.3 traffic, you must log encryption keys to a file during runtime. These keys can then be used with tools like Wireshark to decrypt and inspect the encrypted communications.
For the Solace JavaScript API and Solace Node.js API, you can use the --tls-keylog-file option in Node.js, which logs TLS session keys to a file. For more information, see Node.js TLS Keylog File Option - CLI Documentation.