You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit made the plugin SSL settings consistent with the naming convention defined in the meta issue: elastic/logstash#14905.
It added the following SSL settings:
ssl_enabled: Enable/disable the SSL settings. If not provided, the value is inferred from the hosts' scheme
ssl_certificate: OpenSSL-style X.509 certificate file to authenticate the client
ssl_key: OpenSSL-style RSA private key that corresponds to the ssl_certificate
ssl_truststore_path: The JKS truststore to validate the server's certificate
ssl_truststore_type: The format of the truststore file
ssl_truststore_password: The truststore password
ssl_keystore_path: The keystore used to present a certificate to the server
ssl_keystore_type: The format of the keystore file
ssl_keystore_password: The keystore password
ssl_cipher_suites: The list of cipher suites to use
ssl_supported_protocols: Supported protocols with versions
ssl_verification_mode: Defines how to verify the certificates presented by another party in the TLS connection
And deprecated:
ssl in favor of ssl_enabled
ca_file in favor of ssl_certificate_authorities
keystore in favor of ssl_keystore_path
keystore_password in favor of ssl_keystore_password
-`ssl_enabled`: Enable/disable the SSL settings. If not provided, the value is inferred from the hosts scheme
4
+
-`ssl_certificate`: OpenSSL-style X.509 certificate file to authenticate the client
5
+
-`ssl_key`: OpenSSL-style RSA private key that corresponds to the `ssl_certificate`
6
+
-`ssl_truststore_path`: The JKS truststore to validate the server's certificate
7
+
-`ssl_truststore_type`: The format of the truststore file
8
+
-`ssl_truststore_password`: The truststore password
9
+
-`ssl_keystore_path`: The keystore used to present a certificate to the server
10
+
-`ssl_keystore_type`: The format of the keystore file
11
+
-`ssl_keystore_password`: The keystore password
12
+
-`ssl_cipher_suites`: The list of cipher suites to use
13
+
-`ssl_supported_protocols`: Supported protocols with versions
14
+
-`ssl_verification_mode`: Defines how to verify the certificates presented by another party in the TLS connection
15
+
- Reviewed and deprecated SSL settings to comply with Logstash's naming convention
16
+
- Deprecated `ssl` in favor of `ssl_enabled`
17
+
- Deprecated `ca_file` in favor of `ssl_certificate_authorities`
18
+
- Deprecated `keystore` in favor of `ssl_keystore_path`
19
+
- Deprecated `keystore_password` in favor of `ssl_keystore_password`
20
+
1
21
## 3.14.0
2
22
- Added support for configurable retries with new `retry_on_failure` and `retry_on_status` options [#160](https://github.com/logstash-plugins/logstash-filter-elasticsearch/pull/160)
@@ -121,14 +121,13 @@ The `monitoring` permission at cluster level is necessary to perform periodic co
121
121
[id="plugins-{type}s-{plugin}-options"]
122
122
==== Elasticsearch Filter Configuration Options
123
123
124
-
This plugin supports the following configuration options plus the <<plugins-{type}s-{plugin}-common-options>> described later.
124
+
This plugin supports the following configuration options plus the <<plugins-{type}s-{plugin}-common-options>> and the <<plugins-{type}s-{plugin}-deprecated-options>> described later.
The .cer or .pem files to validate the server's certificate.
385
+
386
+
NOTE: You cannot use this setting and <<plugins-{type}s-{plugin}-ssl_truststore_path>> at the same time.
387
+
388
+
[id="plugins-{type}s-{plugin}-ssl_cipher_suites"]
389
+
===== `ssl_cipher_suites`
390
+
* Value type is a list of <<string,string>>
391
+
* There is no default value for this setting
392
+
393
+
The list of cipher suites to use, listed by priorities.
394
+
Supported cipher suites vary depending on the Java and protocol versions.
395
+
396
+
397
+
[id="plugins-{type}s-{plugin}-ssl_enabled"]
398
+
===== `ssl_enabled`
399
+
400
+
* Value type is <<boolean,boolean>>
401
+
* There is no default value for this setting.
402
+
403
+
Enable SSL/TLS secured communication to Elasticsearch cluster.
404
+
Leaving this unspecified will use whatever scheme is specified in the URLs listed in <<plugins-{type}s-{plugin}-hosts>> or extracted from the <<plugins-{type}s-{plugin}-cloud_id>>.
405
+
If no explicit protocol is specified plain HTTP will be used.
377
406
407
+
[id="plugins-{type}s-{plugin}-ssl_key"]
408
+
===== `ssl_key`
378
409
* Value type is <<path,path>>
379
410
* There is no default value for this setting.
380
411
381
-
The keystore used to present a certificate to the server. It can be either .jks or .p12
412
+
OpenSSL-style RSA private key that corresponds to the <<plugins-{type}s-{plugin}-ssl_certificate>>.
382
413
383
-
[id="plugins-{type}s-{plugin}-keystore_password"]
384
-
===== `keystore_password`
414
+
NOTE: This setting can be used only if <<plugins-{type}s-{plugin}-ssl_certificate>> is set.
Defines how to verify the certificates presented by another party in the TLS connection:
494
+
495
+
`full` validates that the server certificate has an issue date that’s within
496
+
the not_before and not_after dates; chains to a trusted Certificate Authority (CA), and
497
+
has a hostname or IP address that matches the names within the certificate.
498
+
499
+
`none` performs no certificate validation.
500
+
501
+
WARNING: Setting certificate verification to `none` disables many security benefits of SSL/TLS, which is very dangerous. For more information on disabling certificate verification please read https://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf
502
+
391
503
[id="plugins-{type}s-{plugin}-tag_on_failure"]
392
504
===== `tag_on_failure`
393
505
@@ -405,5 +517,57 @@ Tags the event on failure to look up previous log event information. This can be
0 commit comments