TLS / SSL Encryption
By default, clients use Transport Layer Security (TLS) / Secure Sockets Layer (SSL)‑encrypted connections to SAP Integration Suite, advanced event mesh event broker services to allow an exchange of uncompressed (SMF) data or Solace Element Management Protocol (SEMP) data with the event broker using TLS/SSL over single TCP connections instead of plaintext over TCP.
Using TLS/SSL-encrypted connections to an event broker offers:
- Confidentiality—Messages cannot be intercepted in transit.
- Message integrity—Messages cannot be modified or tampered with in transit.
- Server authentication—The connected application is able to verify the server identity.
- Client authentication—optional client certificates can be used as a form of client authentication. For more information, see Client Authorization for Messaging Access.
The following types of applications can establish TLS/SSL-encrypted connections to an event broker:
- Client applications that publish and/or receive messages on the event broker message bus.
Client applications can establish secure TLS/SSL connections to properly configured event brokers using Solace Messaging APIs. This requires:- A trusted server certificate on the event broker.
- The appropriate connection URL scheme and port.
- SMF:
tcps://my.broker:55443(secure) vstcp://my.broker:55555(plain) - WebSocket:
wss://my.broker:443(secure) vsws://my.broker:80(plain)
- Network management applications that manage and monitor the event broker through SEMP requests and replies.
- If the network management application uses SEMP Request Over Message Bus service, which uses a Solace Messaging API to establish a client connection, SEMP requests and replies can be sent over the event broker message bus. A secure connection can be established in the same manner as that used by a client application.
- If the network management application uses SEMP Request over HTTP service, a TCP connection to a port on the event broker allows the application to send SEMP requests wrapped in HTTP to a management interface on the event broker and receive replies to them. For SEMP Request over HTTP service, a secure connection can be created when a server certificate is set on the event broker, a TLS/SSL-secure port is specified (443 by default), and an HTTPS URL scheme is used.
SSL encryption can also be used on Message VPN bridges and bridges established by the Message VPN replication and replication Config-Sync facilities. Using encryption on bridge links helps to ensure that communications between event brokers over bridges are secure.
Cipher Suites
The following cryptographic algorithms are used throughout the life of a TLS/SSL‑encrypted connection:
- Key establishment—This algorithm is used to exchange or agree on the symmetric keys to be used for encrypting and decrypting the data payload during the session. Examples: RSA, Diffie-Hellman (DH and DHE), and Elliptic Curve Diffie-Hellman (ECDH and ECDHE).
- Authentication—This algorithm is the digital signature used to authenticate the server (or client application) by proving possession of the private key matching the certificate presented during connection establishment. Common examples include: Examples: RSA (Rivest-Shamir-Adleman), DSA (Digital Signature Algorithm), and ECDSA (Elliptic Curve Digital Signature Algorithm).
- Encryption—This algorithm encrypts and decrypts payload passed on the secure connection. Examples: ChaCha20 and Advanced Encryption Standard (AES).
- Digest—This algorithm is used to maintain message integrity. Tampering with the message would render the digest invalid. Example: SHA2.
The combination of these four cryptographic algorithms is known as a cipher suite.
For the full list of cipher suites event brokers support, refer to Supported Cipher Suites.
Cipher Suites for Inbound Connections
Event brokers maintain a separate cipher suite list for each of the following inbound TLS connection types when using TLS 1.2 and earlier:
- Network management applications using SEMP to manage the event broker (management connections)
- Client applications connecting to the event broker to publish or receive messages (message backbone connections)
Cipher suites for all inbound management and message backbone connections are selected according to the priority clients associate with each cipher suite.
Cipher Suites for Outbound Connections
Event brokers maintain a separate prioritized cipher suite list for each of the following outbound TLS connection types when using TLS 1.2 and earlier:
- Message VPN and bridge connections
- Replication bridge connections
- Config-sync bridge connections
- Multi-node routing links
In addition, the event broker uses the same cipher suite list for outbound LDAP connections that it uses for inbound management connections.
Cipher suites for all outbound connections (including LDAP connections) are selected according to the priority configured in each corresponding cipher suite list.
Ciphers for SSH Connections
Event brokers maintain a list of ciphers for all SSH, SCP, and SFTP connections. For purposes of encrypted connections, the cipher list has a similar function to a cipher suite list; however, key establishment, authentication, and digest algorithms are not used. For the full list of ciphers event brokers support, refer to Supported Ciphers.
Ciphers for all SSH connections are selected according to the priority clients associate with each cipher.
Supported Cipher Suites
The following table shows the full list of cipher suites event brokers support for inbound and outbound connections when you use TLS 1.2. For information about cipher suites when you use TLS 1.3, see Supported Cipher Suites when using TLS 1.3. The list is sorted from strongest to weakest.
| OpenSSL name | IANA name | Default Security Policy |
|---|---|---|
|
ECDHE-RSA-AES256-GCM-SHA384 |
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
Supported |
|
ECDHE-RSA-AES256-SHA384 |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 |
Supported |
|
ECDHE-RSA-AES256-SHA |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
Supported |
|
AES256-GCM-SHA384 |
TLS_AES_256_GCM_SHA384 |
Supported |
|
AES256-SHA256 |
TLS_RSA_WITH_AES_256_CBC_SHA256 |
Supported |
|
AES256-SHA |
TLS_RSA_WITH_AES_256_CBC_SHA |
Supported |
|
ECDHE-RSA-DES-CBC3-SHA |
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA |
Not Supported |
|
DES-CBC3-SHA |
SSL_RSA_WITH_3DES_EDE_CBC_SHA |
Not Supported |
|
ECDHE-RSA-AES128-GCM-SHA256 |
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
Supported |
|
ECDHE-RSA-AES128-SHA256 |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 |
Supported |
|
ECDHE-RSA-AES128-SHA |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
Supported |
|
AES128-GCM-SHA256 |
TLS_RSA_WITH_AES_128_GCM_SHA256 |
Supported |
|
AES128-SHA256 |
TLS_RSA_WITH_AES_128_CBC_SHA256 |
Supported |
|
AES128-SHA |
TLS_RSA_WITH_AES_128_CBC_SHA |
Supported |
Installing an ECDSA server certificate will break compatibility with older Solace Messaging API and event broker versions that do not support TLS 1.3. Ensure you update all your event broker instances and client applications to support TLS 1.3 before proceeding.
When using TLS 1.2, certificate keys must be at least 1024 bits in length. When using keys shorter than 1024 bits, you may receive a “digest too big for RSA key” error.
Supported Cipher Suites when using TLS 1.3
TLS 1.3 simplifies cipher suite configuration by using just two components:
- An AEAD (Authenticated Encryption with Associated Data) algorithm that protects data during transmission
- A digest algorithm that verifies the security of the initial TLS connection handshake
The following table lists the available TLS 1.3 cipher suites and their corresponding encryption and digest algorithms:
Supported Key Exchange Mechanisms in TLS 1.3
TLS 1.3 uses Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) key exchange with the following supported groups:
- secp256r1
- secp384r1
- secp521r1
- x25519
Supported Authentication Algorithms in TLS 1.3
TLS 1.3 supports two types of authentication algorithms:
- Elliptic Curve Digital Signature Algorithm (ECDSA)—Using curves:
- secp256r1
- secp384r1
- secp521r1
- RSA Probabilistic Signature Scheme (RSASSA-PSS)—Using hash functions:
- SHA-256
- SHA-384
- SHA-512
Supported Ciphers
The following table shows the full list of ciphers event brokers support for SSH connections.
| Ciphers |
Default Security Policy |
|---|---|
|
aes128-ctr |
Supported |
|
aes192-ctr |
Supported |
|
aes256-ctr |
Supported |
|
aes128-gcm@openssh.com |
Supported |
|
aes256-gcm@openssh.com |
Supported |
Supported Signature Algorithms
An event broker can validate a certificate chain if all certificates in the chain are signed with one of the following signature algorithms:
| Signature Algorithm | Default Security Policy | FIPS Compliant Security Policy |
|---|---|---|
|
md2withRSAEncryption md4withRSAEncryption md5withRSAEncryption |
Supported |
Not Supported |
|
shawithRSAEncryption sha1withRSAEncryption sha1withDSAEncryption |
Supported |
Not Supported |
|
sha224withRSAEncryption |
Supported |
Supported (key must be greater than or equal to 2048 bits) |
|
sha224withDSAEncryption |
Supported |
Not Supported |
|
sha256withRSAEncryption |
Supported |
Supported (key must be greater than or equal to 2048 bits) |
|
sha256withDSAEncryption |
Supported |
Not Supported |
|
sha384withRSAEncryption |
Supported |
Supported (key must be greater than or equal to 2048 bits) |
|
sha512withRSAEncryption |
Supported |
Supported (key must be greater than or equal to 2048 bits) |
|
sha224WithECDSAEncryption sha256WithECDSAEncryption sha384WithECDSAEncryption sha512WithECDSAEncryption |
Supported |
Supported |
| Signature Algorithm | Hex Code | Default Security Policy | FIPS Compliant Security Policy |
|---|---|---|---|
|
ecdsa_secp256r1_sha256 |
0x0403 |
Supported |
Supported |
|
ecdsa_secp384r1_sha384 |
0x0503 |
Supported |
Supported |
|
ecdsa_secp521r1_sha512 |
0x0603 |
Supported |
Supported |
|
rsa_pss_pss_sha256 |
0x0809 |
Supported |
Supported |
|
rsa_pss_rsae_sha256 |
0x0804 |
Supported |
Supported |
|
rsa_pss_pss_sha384 |
0x080a |
Supported |
Supported |
|
rsa_pss_rsae_sha384 |
0x0805 |
Supported |
Supported |
|
rsa_pss_pss_sha512 |
0x080b |
Supported |
Supported |
|
rsa_pss_rsae_sha512 |
0x0806 |
Supported |
Supported |
|
rsa_pkcs1_sha256 |
0x0401 |
Supported |
Supported |
|
rsa_pkcs1_sha384 |
0x0501 |
Supported |
Supported |
|
rsa_pkcs1_sha512 |
0x0601 |
Supported |
Supported |
Installing an ECDSA server certificate will break compatibility with older versions of the Solace Messaging APIs and event broker versions that do not support TLS 1.3. Ensure you update all your event broker instances and client applications to support TLS 1.3 before proceeding.