logstash-input-kafka 9.0.0 → 9.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 82a561e76f34f935cb59203d4bc95d1736f04b2405a9d7b9d382bcb2b89bb4ee
-  data.tar.gz: 97a5f7ed0638e3295ef33cca7dbeddf88e91645bd2ce1a5b08a346ccfb3a7c3e
+  metadata.gz: eb49ebda705dced176fd06a124bf8880270bce67ba12f88e47d0f19ae366c355
+  data.tar.gz: 484ed55776e7a35d077a3c6e0dbbf09dc0665583029e8b41748cda8295c9c0b6
 SHA512:
-  metadata.gz: 2c06fa1cd43f3cfb59b11e7f60b0e66ce051122ec338f61310b81ae943db6b71ca5573a3af126d60cec86cbd81f95679f9cc8eb2985a6fc2c537075f0fc68587
-  data.tar.gz: de58c0a4053a123826417a4ad90397bc85ea04d6df09b02547048683529e9fd14d7c7657820629419eae446e2b396b43694ae8662bc5d5f17585ee5f78d51535
+  metadata.gz: 878524cc86c8a791f51c83c0ac86afbb4fbeb4a3e616b14428a604fb9588e0e5bccb883aec7ceb9a0f02ab61f4c21bd56e424afb77923ab0beef2861e75c3456
+  data.tar.gz: '08032ee1e652286bcd58ffd59dd14e77161103132b74c9c0c9ab3798b20732836c5ec7bc51ce9cb86701a3341ed9ad434c0450ef96354f4e2193fc86e8cfe8ba'

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 9.0.1
+  - Added support for `sasl_jaas_config` setting to allow JAAS config per plugin, rather than per JVM [#313](https://github.com/logstash-plugins/logstash-input-kafka/pull/313)
+
 ## 9.0.0
   - Removed obsolete `ssl` option
 

data/docs/index.asciidoc

@@ -61,6 +61,8 @@ The following metadata from Kafka broker are added under the `[@metadata]` field
 * `[@metadata][kafka][key]`: Record key, if any.
 * `[@metadata][kafka][timestamp]`: Timestamp in the Record. Depending on your broker configuration, this can be either when the record was created (default) or when it was received by the broker. See more about property log.message.timestamp.type at https://kafka.apache.org/10/documentation.html#brokerconfigs
 
+Metadata is only added to the event if the `decorate_events` option is set to true (it defaults to false).
+
 Please note that `@metadata` fields are not part of any of your events at output time. If you need these information to be 
 inserted into your original event, you'll have to use the `mutate` filter to manually copy the required fields into your `event`.
 
@@ -103,6 +105,7 @@ https://kafka.apache.org/documentation for more details.
 | <<plugins-{type}s-{plugin}-reconnect_backoff_ms>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-request_timeout_ms>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-retry_backoff_ms>> |<<string,string>>|No
+| <<plugins-{type}s-{plugin}-sasl_jaas_config>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-sasl_kerberos_service_name>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-sasl_mechanism>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-security_protocol>> |<<string,string>>, one of `["PLAINTEXT", "SSL", "SASL_PLAINTEXT", "SASL_SSL"]`|No
@@ -419,6 +422,24 @@ retries are exhausted.
 The amount of time to wait before attempting to retry a failed fetch request
 to a given topic partition. This avoids repeated fetching-and-failing in a tight loop.
 
+[id="plugins-{type}s-{plugin}-sasl_jaas_config"]
+===== `sasl_jaas_config` 
+
+  * Value type is <<string,string>>
+  * There is no default value for this setting.
+
+JAAS configuration setting local to this plugin instance, as opposed to settings using config file configured using `jaas_path`, which are shared across the JVM. This allows each plugin instance to have its own configuration. 
+
+If both `sasl_jaas_config` and `jaas_path` configurations are set, the setting here takes precedence.
+
+Example (setting for Azure Event Hub):
+[source,ruby]
+    input {
+      kafka {
+        sasl_jaas_config => "org.apache.kafka.common.security.plain.PlainLoginModule required username='auser'  password='apassword';"
+      }
+    }
+
 [id="plugins-{type}s-{plugin}-sasl_kerberos_service_name"]
 ===== `sasl_kerberos_service_name` 
 

data/lib/logstash/inputs/kafka.rb

@@ -201,6 +201,8 @@ class LogStash::Inputs::Kafka < LogStash::Inputs::Base
   # `jaas_path` and `kerberos_config`. If this is not desirable, you would have to run separate instances of Logstash on 
   # different JVM instances.
   config :jaas_path, :validate => :path
+  # JAAS configuration settings. This allows JAAS config to be a part of the plugin configuration and allows for different JAAS configuration per each plugin config.
+  config :sasl_jaas_config, :validate => :string
   # Optional path to kerberos config file. This is krb5.conf style as detailed in https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html
   config :kerberos_config, :validate => :path
   # Option to add Kafka metadata like topic, message size to the event.
@@ -355,5 +357,6 @@ class LogStash::Inputs::Kafka < LogStash::Inputs::Base
     end
 
     props.put("sasl.kerberos.service.name",sasl_kerberos_service_name) unless sasl_kerberos_service_name.nil?
+    props.put("sasl.jaas.config", sasl_jaas_config) unless sasl_jaas_config.nil?
   end
 end #class LogStash::Inputs::Kafka

data/logstash-input-kafka.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name            = 'logstash-input-kafka'
-  s.version         = '9.0.0'
+  s.version         = '9.0.1'
   s.licenses        = ['Apache-2.0']
   s.summary         = "Reads events from a Kafka topic"
   s.description     = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-input-kafka
 version: !ruby/object:Gem::Version
-  version: 9.0.0
+  version: 9.0.1
 platform: ruby
 authors:
 - Elasticsearch
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2019-01-11 00:00:00.000000000 Z
+date: 2019-07-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement