Session caching

Start of changeThe SSLv2, SSLv3, TLSv1, TLSv1.1, and TLSv1.2 protocolsEnd of change can cache session information based on the Start of changeTLSEnd of change Session ID (SID). Start of changeTLSEnd of change connections can request that a previous session be resumed. When session information is found in the cache, connections can use the Start of changeTLS abbreviatedEnd of change handshake, which requires less processing.

Start of changeIn a similar manner, the TLSv1.3 protocol can cache session information based on a session ticket. TLS connections can request that a previous session be resumed. When session information is found in the cache, connections can use an abbreviated handshake which avoids public key encryption. End of change

The number of SIDs Start of changeor session ticketsEnd of change cached, the length of time that a SID Start of changeor session ticketEnd of change is held in the cache, and whether Start of changeSIDs inEnd of change the cache are available across the sysplex can be configured using the TTLSGskAdvancedParms statement. Start of changeTLS Version 1.3 session tickets are not shared across the sysplex.End of change

Start of changeSession ticket generation and caching for TLS Version 1.3 can be enabled for the client and server using the TTLSGskAdvancedParms statement. The maximum size of the session ticket accepted by the client, the algorithm used by the server to encrypt the session ticket, the number of session tickets that the server sends after an initial handshake completes, and the maximum time for which a session ticket is valid for session resumption can also be configured using the TTLSGskAdvancedParms statement.End of change