public static final class TLS13PostHandshakeConfig.TLS13NewSessionTicketConfig extends TLS13PostHandshakeConfig implements java.lang.Cloneable
NEW_SESSION_TICKET
.
At at time after the regular handshake has been finished a server can send one or more NewSessionTicket messages to client. Each NewSessionTicket message contains a ticket the client may use to later indicate a session it wants to resume.
To trigger the sending of a NewSessionTicket message a server may specify
a TLS13NewSessionTicketConfig object when calling method
postHandshake
on the SSLSocket communicating with the client:
SSLSocket sslSocket = ...; ... TLS13NewSessionTicketConfig newSessionTicketConfig = new TLS13NewSessionTicketConfig(); sslSocket.postHandshake(newSessionTicketConfig); ...It may be of advantage to trigger the sending of a NewSessionTicket message during writing data to the client:
SSLSocket sslSocket = ...; ... TLS13NewSessionTicketConfig newSessionTicketConfig = new TLS13NewSessionTicketConfig(); sslSocket.postHandshake(newSessionTicketConfig); ...If the server wants to send more than on ticket, it can tell iSaSiLk to do so by specifying the number of tickets within the NewSessionTicket configuration:
SSLSocket sslSocket = ...; ... int numberOfTicketsToBeSent = 2; TLS13NewSessionTicketConfig newSessionTicketConfig = new TLS13NewSessionTicketConfig(numberOfTicketsToBeSent); sslSocket.postHandshake(newSessionTicketConfig); ...The number of tickets to be send also can be configured by the iSaSiLk
SessionManager
. However, the SessionManager settings will only have impact on the number tickets
automatically sent by iSaSiLk after having successfully completed a handshake and not by
NewSessionTciket messages that have been explicitly triggered
by an application.TLS13PostHandshakeConfig.TLS13KeyUpdateConfig, TLS13PostHandshakeConfig.TLS13NewSessionTicketConfig, TLS13PostHandshakeConfig.TLS13PostHandshakeAuthConfig
KEY_UPDATE, NEW_SESSION_TICKET, POST_HANDSHAKE_AUTH
Constructor and Description |
---|
TLS13NewSessionTicketConfig()
Default constructor.
|
Modifier and Type | Method and Description |
---|---|
java.lang.Object |
clone()
Returns a clone of this TLS13PostHandshakeAuthConfig.
|
void |
setNumberOfTicketsToBeSent(int n)
Sets the number of tickets to be sent to the client.
|
setMaxNumberOfPostHandshakeMessages, setMaxNumberOfSubsequentPostHandshakeMessages
public TLS13NewSessionTicketConfig()
public void setNumberOfTicketsToBeSent(int n)
In TLS 1.3, after having successfully established a session the server can send one or more NewSessionTicket messages to client. Each NewSessionTicket message contains a ticket the client may use to later indicate a session it wants to resume. With this method the number of tickets (and therefore NewSessionTicket) messages can be configured that a TLS 1.3 server shall send to the client. Each NewSessionTicket message will contain a new ticket but will refer to the same base session to may be resumed later on.
n
- the number of tickets to be sent to the client (default: 1).public java.lang.Object clone()
clone
in class TLS13PostHandshakeConfig