Creating Secure Sessions
Clients can optionally create secure sessions that require trusted server certificates to establish a TLS/SSL-encrypted client connection to a Solace event broker. When a secure session is created, SMF information is transported using TLS/SSL over TCP instead of plain-text over TCP.
To create a secure session, a number of TLS/SSL-specific session properties must be specified as discussed below. In addition, the event broker that the secure session will connect to must be properly configured, and the appropriate server certificate must be in place. For information on configuring an event broker to allow for secure connections, see TLS / SSL Service Configuration.
Related Samples
For an example of how to create and connect secure sessions, see the SecureSession sample for the Solace Java RTO API. Also, you can use secure sessions on other samples by prepending "tcps:" to the hostname used in the sample (see Host).
TLS/SSL-Specific Properties
To create a secure session, the following session properties must configured.
| Property | Use | Description |
|---|---|---|
|
Host |
Solace Java RTO API: |
Each host entry for a TLS/SSL connection requires an appropriate TLS/SSL protocol, and a specific TLS/SSL port number can optionally be specified. If no port number is specified, the default port of 55443 is used. For information on configuring hosts, see Host. |
| Configuring Minimum and Maximum SSL Protocols |
Solace Java RTO API: |
These properties specify the oldest (minimum) and most recent (maximum) TLS protocols supported. Possible values are:
The default minimum TLS protocol is TLS v1.2. The minimum and maximum TLS protocol version properties cannot be combined with the deprecated SSL excluded protocols properties. |
|
SSL Certificate Validation |
Solace Java RTO API: |
Indicates that whether the API should validate server certificates with the trusted certificates in the trust store. The trust store is a directory on a server that contains the trusted certificates. The default value for this property is |
|
SSL Certificate Date Validation |
Solace Java RTO API: |
Indicates whether the session connection should fail when an expired certificate or a certificate not yet in use is received. The default is No certificate date validation is performed if the SSL certificate validation property is set to |
| SSL Certificate Host Validation (SSL Server Certificate Validation Using Subject-Alternative Name) |
Solace Java RTO API: |
Indicates if the session connection validates the subject alternative name in the X.509 certificate. If the X.509 certificate does not contain the subject alternative name section, the common name in the subject field of the X.509 certificate is verified against the HOST property. The default and recommended setting is No certificate host validation is performed if the SSL certificate validation property is set to |
|
SSL Cipher Suites |
Solace Java RTO API: |
A comma-separated list of cipher suites, listed in order of importance, to use to negotiate with the event broker. A cipher suite is a combination of cryptographic parameters that define the security algorithms and key sizes used for authentication, key agreement, encryption, and integrity protection. For a listing of the supported cipher suites in order of preference, see Solace Messaging APIs for the Solace Java RTO API. By default, no cipher suites are listed, which indicates that all supported ciphers should be considered. If your application negotiates a TLS 1.3 connection, you cannot select which cipher suites to negotiate with the event broker and these properties are ignored. |
|
SSL Trusted Store Directory |
Solace Java RTO API: |
The directory where trusted certificates are stored. The network directory where the trusted certificates are stored. |
|
SSL Connection Downgrade To |
Solace Java RTO API: |
Indicates that the SSL connection should be downgraded following client authentication. Allowed transport protocols for SSL connection downgrade To property are: "PLAIN_TEXT". This property is optional. |