This engine factory is a bridge for TLSServerEngine param configurations which use a () => Engine interface.
SslServerConfiguration represents the collection of parameters that an engine factory should use to configure a TLS server Engine.
SslServerConfiguration represents the collection of parameters that an engine factory should use to configure a TLS server Engine.
The credentials used by the server engine to verify itself to a remote peer.
Determines whether mutual authentication is desired or required by this server engine.
The credentials used by the server engine to validate a remote peer's credentials.
The cipher suites which should be used by a particular server engine.
The protocols which should be enabled for use with a particular server engine.
The ALPN or NPN protocols which should be supported by a particular server engine.
Instances of this class provide a method to create server Finagle Engines for use with TLS.
SslServerSessionVerifier represents an opportunity for a user or system to perform additional server-side verification checks against a configuration or session.
SslServerSessionVerifier represents an opportunity for a user or system
to perform additional server-side verification checks against a
configuration or session. The apply
method of the verifier is called
when an SSLSession
has been established.
This engine factory is a default JVM-based implementation, intended to provide coverage for a wide array of configurations.
This engine factory is intended to act as a temporary bridge for those currently using non-PKCS#8 PEM-encoded keys, such as PKCS#1 keys.
This engine factory is intended to act as a temporary bridge for those currently using
non-PKCS#8 PEM-encoded keys, such as PKCS#1 keys. Once the private key file has been
converted into PKCS#8 PEM-encoded format, JdkServerEngineFactory or
Netty4ServerEngineFactory
should be used instead.
(Since version 2017-02-10) Use Netty4ServerEngineFactory instead
This engine factory uses PEMEncodedKeyManager which shells out to OpenSSL in order to convert the key into a usable format.
This engine factory is intended to act as a temporary bridge for those currently using JSSE or OpenSSL (Finagle-Native) through the Ssl class.
This engine factory is intended to act as a temporary bridge for those currently using
JSSE or OpenSSL (Finagle-Native) through the Ssl class. From there, if using
JSSE, then JdkServerEngineFactory or Netty4ServerEngineFactory
should be the next
step. If using OpenSSL, then Netty4ServerEngineFactory
should be the next
step, as it will be the supported path forward for using native engines with Finagle.
(Since version 2017-02-07) Use Netty4ServerEngineFactory instead
This engine factory is a bridge for TLSServerEngine param configurations which use a () => Engine interface. It should only be used for legacy purposes.