Akka HTTP supports TLS encryption on the client-side as well as on the server-side.
// ConnectionContext def https( sslContext: SSLContext, sslConfig: Option[AkkaSSLConfig] = None, enabledCipherSuites: Option[immutable.Seq[String]] = None, enabledProtocols: Option[immutable.Seq[String]] = None, clientAuth: Option[TLSClientAuth] = None, sslParameters: Option[SSLParameters] = None, http2: UseHttp2 = UseHttp2.Negotiated) = new HttpsConnectionContext(sslContext, sslConfig, enabledCipherSuites, enabledProtocols, clientAuth, sslParameters, http2)
// ConnectionContext /** Used to serve HTTPS traffic. */ def https(sslContext: SSLContext): HttpsConnectionContext = scaladsl.ConnectionContext.https(sslContext) /** Used to serve HTTPS traffic. */ def https( sslContext: SSLContext, sslConfig: Optional[AkkaSSLConfig], enabledCipherSuites: Optional[JCollection[String]], enabledProtocols: Optional[JCollection[String]], clientAuth: Optional[TLSClientAuth], sslParameters: Optional[SSLParameters]) = scaladsl.ConnectionContext.https( sslContext, OptionConverters.toScala(sslConfig), OptionConverters.toScala(enabledCipherSuites).map(Util.immutableSeq(_)), OptionConverters.toScala(enabledProtocols).map(Util.immutableSeq(_)), OptionConverters.toScala(clientAuth), OptionConverters.toScala(sslParameters))
In addition to the
cachedHostConnectionPool methods the akka.http.scaladsl.Httpakka.http.javadsl.Http extension also defines
cachedHostConnectionPoolHttps. These methods work identically to their counterparts without the
-Https suffix, with the exception that all connections will always be encrypted.
superPool methods determine the encryption state via the scheme of the incoming request, i.e. requests to an “https” URI will be encrypted, while requests to an “http” URI won’t.
The encryption configuration for all HTTPS connections, i.e. the
HttpsContext is determined according to the following logic:
- If the optional
httpsContextmethod parameter is defined it contains the configuration to be used (and thus takes precedence over any potentially set default client-side
- If the optional
httpsContextmethod parameter is undefined (which is the default) the default client-side
HttpsContextis used, which can be set via the
setDefaultClientHttpsContexton the HttpHttpHttpHttp extension.
- If no default client-side
HttpsContexthas been set via the
setDefaultClientHttpsContexton the HttpHttpHttpHttp extension the default system configuration is used.
Usually the process is, if the default system TLS configuration is not good enough for your application’s needs, that you configure a custom
HttpsContext instance and set it via
Http.get(system).setDefaultClientHttpsContext. Afterwards you simply use
singleRequest without a specific
httpsContext argument, which causes encrypted connections to rely on the configured default client-side
If no custom
HttpsContext is defined the default context uses Java’s default TLS settings. Customizing the
HttpsContext can make the Https client less secure. Understand what you are doing!
Akka HTTP heavily relies on, and delegates most configuration of any SSL/TLS related options to Lightbend SSL-Config, which is a library specialized in providing an secure-by-default SSLContext and related options.
Please refer to the Lightbend SSL-Config documentation for detailed documentation of all available settings.
SSL Config settings used by Akka HTTP (as well as Streaming TCP) are located under the akka.ssl-config namespace.
Akka HTTP relies on Lightbend SSL-Config which is a library maintained by Lightbend that makes configuring things related to SSL/TLS much simpler than using the raw SSL APIs provided by the JDK. Please refer to its documentation to learn more about it.
All configuration options available to this library may be set under the
akka.ssl-config configuration for Akka HTTP applications.
When encountering problems connecting to HTTPS hosts we highly encourage to reading up on the excellent ssl-config configuration. Especially the quick start sections about adding certificates to the trust store should prove very useful, for example to easily trust a self-signed certificate that applications might use in development mode.
While it is possible to disable certain checks using the so called “loose” settings in SSL Config, we strongly recommend to instead attempt to solve these issues by properly configuring TLS–for example by adding trusted keys to the keystore.
If however certain checks really need to be disabled because of misconfigured (or legacy) servers that your application has to speak to, instead of disabling the checks globally (i.e. in
application.conf) we suggest configuring the loose settings for specific connections that are known to need them disabled (and trusted for some other reason). The pattern of doing so is documented in the following sub-sections.
Hostname verification proves that the Akka HTTP client is actually communicating with the server it intended to communicate with. Without this check a man-in-the-middle attack is possible. In the attack scenario, an alternative certificate would be presented which was issued for another host name. Checking the host name in the certificate against the host name the connection was opened against is therefore vital.
HttpsContext enables hostname verification. Akka HTTP relies on the Lightbend SSL-Config library to implement this and security options for SSL/TLS. Hostname verification is provided by the JDK and used by Akka since Java 7, and on Java 6 the verification is implemented by ssl-config manually.
For further recommended reading we would like to highlight the fixing hostname verification blog post by blog post by Will Sargent.
SNI is an TLS extension which aims to guard against man-in-the-middle attacks. It does so by having the client send the name of the virtual domain it is expecting to talk to as part of the TLS handshake.
It is specified as part of RFC 6066.
It is highly discouraged to disable any of the security features of TLS, however do acknowledge that workarounds may sometimes be needed.
Before disabling any of the features one should consider if they may be solvable within the TLS world, for example by trusting a certificate, or configuring the trusted cipher suites. There’s also a very important section in the ssl-config docs titled LooseSSL - Please read this before turning anything off!.
If disabling features is indeed desired, we recommend doing so for specific connections, instead of globally configuring it via
The following shows an example of disabling SNI for a given connection:
implicit val system = ActorSystem() implicit val mat = ActorMaterializer() // WARNING: disabling SNI is a very bad idea, please don't unless you have a very good reason to. val badSslConfig = AkkaSSLConfig().mapSettings(s => s.withLoose(s.loose.withDisableSNI(true))) val badCtx = Http().createClientHttpsContext(badSslConfig) Http().outgoingConnectionHttps(unsafeHost, connectionContext = badCtx)
final ActorSystem system = ActorSystem.create(); final ActorMaterializer mat = ActorMaterializer.create(system); final Http http = Http.get(system); // WARNING: disabling SNI is a very bad idea, please don't unless you have a very good reason to. final AkkaSSLConfig defaultSSLConfig = AkkaSSLConfig.get(system); final AkkaSSLConfig badSslConfig = defaultSSLConfig .convertSettings(s -> s.withLoose(s.loose().withDisableSNI(true))); final HttpsConnectionContext badCtx = http.createClientHttpsContext(badSslConfig); http.outgoingConnection(ConnectHttp.toHostHttps(unsafeHost).withCustomHttpsContext(badCtx));
badSslConfig is a copy of the default
AkkaSSLConfig with the slightly changed configuration to disable SNI. This value can be cached and used for connections which should indeed not use this feature.