|Enable/Disable HTTP connector.|
|Enable/Disable HTTPS connector.|
Although not recommended, the HTTP and HTTPS connectors can both be enabled at a time. The respective ports are configurable using
druid.tlsPort properties on each process. Please see
Configuration section of individual processes to check the valid and default values for these ports.
Jetty server configuration
Apache Druid uses Jetty as its embedded web server.
To get familiar with TLS/SSL, along with related concepts like keys and certificates, read Configuring Secure Protocols in the Jetty documentation. To get more in-depth knowledge of TLS/SSL support in Java in general, refer to the Java Secure Socket Extension (JSSE) Reference Guide. The Class SslContextFactory reference doc can help in understanding TLS/SSL configurations listed below. Finally, Java Cryptography Architecture Standard Algorithm Name Documentation for JDK 8 lists all possible values for the configs below, among others provided by Java implementation.
|The file path or URL of the TLS/SSL Key store.||none||yes|
|The type of the key store.||none||yes|
|Alias of TLS/SSL certificate for the connector.||none||yes|
|The Password Provider or String password for the Key Store.||none||yes|
|Should Druid server detect Key Store file change and reload.||false||no|
|How frequently should Druid server scan for Key Store file change.||60||yes|
The following table contains configuration options related to client certificate authentication.
|If set to true, clients must identify themselves by providing a TLS certificate, without which connections will fail.||false||no|
|If set to true, clients may optionally identify themselves by providing a TLS certificate. Connections will not fail if TLS certificate is not provided. This property is ignored if ||false||no|
|The type of the trust store containing certificates used to validate client certificates. Not needed if ||no|
|The file path or URL of the trust store containing certificates used to validate client certificates. Not needed if ||none||yes, only if |
|Algorithm to be used by TrustManager to validate client certificate chains. Not needed if ||no|
|The password provider or String password for the Trust Store. Not needed if ||none||no|
|If set to true, check that the client's hostname matches the CN/subjectAltNames in the client certificate. Not used if ||true||no|
|Specifies a path to a file containing static Certificate Revocation Lists, used to check if a client certificate has been revoked. Not used if ||null||no|
The following table contains non-mandatory advanced configuration options, use caution.
|Algorithm to use for creating KeyManager, more details here.||no|
|The Password Provider or String password for the Key Manager.||none||no|
|List of cipher suite names to include. You can either use the exact cipher suite name or a regular expression.||Jetty's default include cipher list||no|
|List of cipher suite names to exclude. You can either use the exact cipher suite name or a regular expression.||Jetty's default exclude cipher list||no|
|List of exact protocols names to include.||Jetty's default include protocol list||no|
|List of exact protocols names to exclude.||Jetty's default exclude protocol list||no|
Internal communication over TLS
Whenever possible Druid processes will use HTTPS to talk to each other. To enable this communication Druid's HttpClient needs to be configured with a proper SSLContext that is able to validate the Server Certificates, otherwise communication will fail.
Since, there are various ways to configure SSLContext, by default, Druid looks for an instance of SSLContext Guice binding while creating the HttpClient. This binding can be achieved writing a Druid extension which can provide an instance of SSLContext. Druid comes with a simple extension present here which should be useful enough for most simple cases, see this for how to include extensions. If this extension does not satisfy the requirements then please follow the extension implementation to create your own extension.
When Druid Coordinator/Overlord have both HTTP and HTTPS enabled and Client sends request to non-leader process, then Client is always redirected to the HTTPS endpoint on leader process. So, Clients should be first upgraded to be able to handle redirect to HTTPS. Then Druid Overlord/Coordinator should be upgraded and configured to run both HTTP and HTTPS ports. Then Client configuration should be changed to refer to Druid Coordinator/Overlord via the HTTPS endpoint and then HTTP port on Druid Coordinator/Overlord should be disabled.
Custom certificate checks
Druid supports custom certificate check extensions. Please refer to the
org.apache.druid.server.security.TLSCertificateChecker interface for details on the methods to be implemented.
To use a custom TLS certificate checker, specify the following property:
|Type name of custom TLS certificate checker, provided by extensions. Please refer to extension documentation for the type name that should be specified.||"default"||no|
The default checker delegates to the standard trust manager and performs no additional actions or checks.
If using a non-default certificate checker, please refer to the extension documentation for additional configuration properties needed.