How do I prevent QIE from caching SSL Sessions in a secure socket

0 votes
asked Dec 4, 2018 by ben-s-7515 (12,640 points)
We need to send messages to another system using a secure socket destionation.  The remote system does not support re-using sessions, and throws an exception when the system tries to connect and send a second message after the channel starts.  The logs show that on the second message, a sessionId is passed in the TLS handshake.  How do I force QIE to use a new session for every message send on the Secure Socket destination node?

1 Answer

0 votes

NOTE: Forcing QIE to use a new TLS Session with each connection can effect performance of the connection speed because a new TLS handshake will be required with each message.

QIE has been enhanced to allow for a java option to prevent the re-use of the TLS Session.  Starting with build #9954, QIE will check for a java option, if the option is set to true, then it will not cache TLS sessions, and force a new handshake on every message sent across the secure socket connection.

To set this option, first note the 'Host' and 'Port' from the destionation node. 

Then open the QIEService Properties dialog and go to the 'Startup' tab.  From this tab, add the following java option to the 'Arguments' field.


Replace the '{host}' with what is found in the destination host field, and replace the '{port}' with what is found in the destination port field.  For example would be the java option for the above destination node.


answered Dec 4, 2018 by ben-s-7515 (12,640 points)
edited Dec 5, 2018 by brandon-w-8204