This class encapsulates context information for an SSL server or client, such as the certificate verification mode and the location of certificates and private key files, as well as the list of supported ciphers.

The Context class is also used to control SSL session caching on the server and client side.

A Note Regarding TLSv1.3 Support:

TLSv1.3 support requires at least OpenSSL version 1.1.1. Make sure that the TLSv1.3 cipher suites are enabled:

• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• TLS_AES_128_GCM_SHA256
• TLS_AES_128_CCM_8_SHA256
• TLS_AES_128_CCM_SHA256

The first three of the above cipher suites should be enabled by default in OpenSSL if you do not provide an explicit cipher configuration (cipherList).

Context is used by a client for TLSv1 or higher. Use requireMinimumProtocol() or disableProtocols() to disable undesired older versions.

Context is used by a client for TLSv1 or higher. Use requireMinimumProtocol() or disableProtocols() to disable undesired older versions.

DEPRECATED. Context is used by a client.

DEPRECATED. Context is used by a server.

DEPRECATED. Context is used by a client requiring TLSv1.

DEPRECATED. Context is used by a server requiring TLSv1.

DEPRECATED. Context is used by a client requiring TLSv1.1 (OpenSSL 1.0.0 or newer).

DEPRECATED. Context is used by a server requiring TLSv1.1 (OpenSSL 1.0.0 or newer).

DEPRECATED. Context is used by a client requiring TLSv1.2 (OpenSSL 1.0.1 or newer).

DEPRECATED. Context is used by a server requiring TLSv1.2 (OpenSSL 1.0.1 or newer).

DEPRECATED. Context is used by a client requiring TLSv1.3 (OpenSSL 1.1.1 or newer).

DEPRECATED. Context is used by a server requiring TLSv1.3 (OpenSSL 1.1.1 or newer).

Server: The server will not send a client certificate request to the client, so the client will not send a certificate.

Client: If not using an anonymous cipher (by default disabled), the server will send a certificate which will be checked, but the result of the check will be ignored.

Server: The server sends a client certificate request to the client. The certificate returned (if any) is checked. If the verification process fails, the TLS/SSL handshake is immediately terminated with an alert message containing the reason for the verification failure.

Client: The server certificate is verified, if one is provided. If the verification process fails, the TLS/SSL handshake is immediately terminated with an alert message containing the reason for the verification failure.

Server: If the client did not return a certificate, the TLS/SSL handshake is immediately terminated with a handshake failure alert.

Client: Same as VERIFY_RELAXED.

Server: Only request a client certificate on the initial TLS/SSL handshake. Do not ask for a client certificate again in case of a renegotiation.

Client: Same as VERIFY_RELAXED.

Creates a Context using the given parameters.

• usage specifies whether the context is used by a client or server.
• params specifies the context parameters.

Creates a Context.

• usage specifies whether the context is used by a client or server.
• caLocation contains the path to the file or directory containing the CA/root certificates. Can be empty if the OpenSSL builtin CA certificates are used (see loadDefaultCAs).
• verificationMode specifies whether and how peer certificates are validated.
• verificationDepth sets the upper limit for verification chain sizes. Verification will fail if a certificate chain larger than this is encountered.
• loadDefaultCAs specifies whether the builtin CA certificates from OpenSSL are used.
• cipherList specifies the supported ciphers in OpenSSL notation.

Note that a private key and/or certificate must be specified with usePrivateKey()/useCertificate() before the Context can be used.

Creates a Context.

• usage specifies whether the context is used by a client or server.
• privateKeyFile contains the path to the private key file used for encryption. Can be empty if no private key file is used.
• certificateFile contains the path to the certificate file (in PEM format). If the private key and the certificate are stored in the same file, this can be empty if privateKeyFile is given.
• caLocation contains the path to the file or directory containing the CA/root certificates. Can be empty if the OpenSSL builtin CA certificates are used (see loadDefaultCAs).
• verificationMode specifies whether and how peer certificates are validated.
• verificationDepth sets the upper limit for verification chain sizes. Verification will fail if a certificate chain larger than this is encountered.
• loadDefaultCAs specifies whether the builtin CA certificates from OpenSSL are used.
• cipherList specifies the supported ciphers in OpenSSL notation.

Note: If the private key is protected by a passphrase, a PrivateKeyPassphraseHandler must have been setup with the SSLManager, or the SSLManager's PrivateKeyPassphraseRequired event must be handled.

Destroys the Context.

Add one trusted certification authority to be used by the Context.

Adds a certificate for certificate chain validation.

Disables the given protocols.

The protocols to be disabled are specified by OR-ing values from the Protocols enumeration, e.g.:

context.disableProtocols(PROTO_SSLV2 | PROTO_SSLV3);

Newer versions of OpenSSL support RFC 4507 tickets for stateless session resumption.

The feature can be disabled by calling this method.

Enable or disable the automatic post-connection extended certificate verification.

See X509Certificate::verify() for more information.

Enable or disable SSL/TLS session caching. For session caching to work, it must be enabled on the server, as well as on the client side.

The default is disabled session caching.

To enable session caching on the server side, use the two-argument version of this method to specify a session ID context.

Enables or disables SSL/TLS session caching on the server. For session caching to work, it must be enabled on the server, as well as on the client side.

SessionIdContext contains the application's unique session ID context, which becomes part of each session identifier generated by the server within this context. SessionIdContext can be an arbitrary sequence of bytes with a maximum length of SSL_MAX_SSL_SESSION_ID_LENGTH.

A non-empty sessionIdContext should be specified even if session caching is disabled to avoid problems with clients requesting to reuse a session (e.g. Firefox 3.6).

This method may only be called on SERVER_USE Context objects.

Returns true if and only if automatic extended certificate verification is enabled.

Flushes the SSL session cache on the server.

This method may only be called on SERVER_USE Context objects.

Returns the InvalidCertificateHandler set for this Context, or a null pointer if none has been set.

Returns the current maximum size of the server session cache.

This method may only be called on SERVER_USE Context objects.

Returns the timeout (in seconds) of cached sessions on the server.

This method may only be called on SERVER_USE Context objects.

Enable or disable SSL/TLS SSL_OP_IGNORE_UNEXPECTED_EOF

Some TLS implementations do not send the mandatory close_notify alert on shutdown. If the application tries to wait for the close_notify alert but the peer closes the connection without sending it, an error is generated. When this option is enabled the peer does not need to send the close_notify alert and a closed connection will be treated as if the close_notify alert was received.

Returns true if and only if the context is for use by a server.

Returns true if automatic OCSP response reception and verification is enabled for client connections

When choosing a cipher, use the server's preferences instead of the client preferences. When not called, the SSL server will always follow the clients preferences. When called, the SSL/TLS server will choose following its own preferences.

Disables all protocol version lower than the given one. To require at least TLS 1.2 or later:

context.requireMinimumProtocol(PROTO_TLSV1_2);

Returns true if and only if the session cache is enabled.

Sets a Context-specific InvalidCertificateHandler.

If specified, this InvalidCertificateHandler will be used instead of the one globally set in the SSLManager.

Normally, when an SSL connection is finished, the parties must send out close_notify alert messages for a clean shutdown. When setting the "quiet shutdown" flag to true, the SecureSocketImpl::shutdown() will set the SSL shutdown flags, but no close_notify alert is sent to the peer. This behaviour violates the TLS standard. The default is a normal shutdown behaviour as described by the TLS standard.

Sets the security level.

Sets the maximum size of the server session cache, in number of sessions. The default size (according to OpenSSL documentation) is 1024*20, which may be too large for many applications, especially on embedded platforms with limited memory.

Specifying a size of 0 will set an unlimited cache size.

This method may only be called on SERVER_USE Context objects.

Sets the timeout (in seconds) of cached sessions on the server. A cached session will be removed from the cache if it has not been used for the given number of seconds.

This method may only be called on SERVER_USE Context objects.

Returns the underlying OpenSSL SSL Context object.

Returns whether the context is for use by a client or by a server and whether TLSv1 is required.

Sets the certificate to be used by the Context.

To set-up a complete certificate chain, it might be necessary to call addChainCertificate() to specify additional certificates.

Note that useCertificate() must always be called before usePrivateKey().

Deprecated. This function is deprecated and should no longer be used.

Sets the private key to be used by the Context.

Note that useCertificate() must always be called before usePrivateKey().

Note: If the private key is protected by a passphrase, a PrivateKeyPassphraseHandler must have been setup with the SSLManager, or the SSLManager's PrivateKeyPassphraseRequired event must be handled.

Sets the private key to be used by the Context.

Note that useCertificate() must always be called before usePrivateKey().

Note: If the private key is protected by a passphrase, a PrivateKeyPassphraseHandler must have been setup with the SSLManager, or the SSLManager's PrivateKeyPassphraseRequired event must be handled.

Returns the verification mode.