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
@@ -158,13 +160,13 @@ at the TCP layer and IPs will not be resolved to hostnames.
158
160
[id="plugins-{type}s-{plugin}-ecs_compatibility"]
159
161
===== `ecs_compatibility`
160
162
161
-
* Value type is <<string,string>>
162
-
* Supported values are:
163
-
** `disabled`: unstructured connection metadata added at root level
164
-
** `v1`,`v8`: structured connection metadata added under `[@metadata][input][tcp]`
165
-
* Default value depends on which version of Logstash is running:
166
-
** When Logstash provides a `pipeline.ecs_compatibility` setting, its value is used as the default
167
-
** Otherwise, the default value is `disabled`.
163
+
* Value type is <<string,string>>
164
+
* Supported values are:
165
+
** `disabled`: unstructured connection metadata added at root level
166
+
** `v1`,`v8`: structured connection metadata added under `[@metadata][input][tcp]`
167
+
* Default value depends on which version of Logstash is running:
168
+
** When Logstash provides a `pipeline.ecs_compatibility` setting, its value is used as the default
169
+
** Otherwise, the default value is `disabled`.
168
170
169
171
Controls this plugin's compatibility with the https://www.elastic.co/guide/en/ecs/current/index.html[Elastic Common Schema (ECS)].
170
172
The value of this setting affects the <<plugins-{type}s-{plugin}-ecs_metadata,placement of a TCP connection's metadata>> on events.
@@ -224,6 +226,18 @@ to the connecting clients.
224
226
Validate client certificate or certificate chain against these authorities.
225
227
You can define multiple files or paths. All the certificates will be read and added to the trust store.
226
228
229
+
[id="plugins-{type}s-{plugin}-ssl_cipher_suites"]
230
+
===== `ssl_cipher_suites`
231
+
232
+
* Value type is <<string,string>>
233
+
* Default value includes _all_ cipher suites enabled by the JDK and depends on JDK configuration
234
+
235
+
Supported cipher suites vary depending on Java version used, and entries look like `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`.
236
+
For more information, see Oracle’s https://docs.oracle.com/en/java/javase/11/security/oracle-providers.html#GUID-7093246A-31A3-4304-AC5F-5FB6400405E2[JDK SunJSSE provider documentation] and
237
+
the table of supported https://docs.oracle.com/en/java/javase/11/docs/specs/security/standard-names.html#jsse-cipher-suite-names[Java cipher suite names].
238
+
239
+
NOTE: To check the supported cipher suites locally run the following script: `$LS_HOME/bin/ruby -e 'p javax.net.ssl.SSLServerSocketFactory.getDefault.getSupportedCipherSuites'`.
240
+
227
241
[id="plugins-{type}s-{plugin}-ssl_enable"]
228
242
===== `ssl_enable`
229
243
@@ -258,6 +272,20 @@ The path to the private key corresponding to the specified certificate (PEM form
0 commit comments