[jira] [Updated] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Long for schema-less case

2020-09-01 Thread Oleksandr Diachenko (Jira) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-10457:

Summary: JsonConverter.toConnectData trims BigInteger to Long for 
schema-less case  (was: JsonConverter.toConnectData trims BigInteger to Double 
for schema-less case)

> JsonConverter.toConnectData trims BigInteger to Long for schema-less case
> -
>
> Key: KAFKA-10457
> URL: https://issues.apache.org/jira/browse/KAFKA-10457
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.7.0
>
>
>  
> When _JsonConverter_ is configured with _schemas.enable=false_ and value, 
> exceeding _Double_ is passed, the result is incorrect since the converter 
> trims it to _Double:_
> {code:java}
> Map props = Collections.singletonMap("schemas.enable", 
> false);
> converter.configure(props, true);
> BigInteger value = BigInteger.valueOf(Long.MAX_VALUE).add(new 
> BigInteger("1"));
> String msg = value.toString();
> SchemaAndValue schemaAndValue = converter.toConnectData(TOPIC, 
> msg.getBytes());
> assertNull(schemaAndValue.schema());
> assertEquals(value, schemaAndValue.value());
> {code}
>  
>  Fails with:
>  
> {code:java}
> expected:<9223372036854775808> but was:<-9223372036854775808>
> Expected :9223372036854775808
> Actual :-9223372036854775808
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Double for schema-less case

2020-09-01 Thread Oleksandr Diachenko (Jira) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-10457:

Priority: Critical  (was: Major)

> JsonConverter.toConnectData trims BigInteger to Double for schema-less case
> ---
>
> Key: KAFKA-10457
> URL: https://issues.apache.org/jira/browse/KAFKA-10457
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.7.0
>
>
>  
> When _JsonConverter_ is configured with _schemas.enable=false_ and value, 
> exceeding _Double_ is passed, the result is incorrect since the converter 
> trims it to _Double:_
> {code:java}
> Map props = Collections.singletonMap("schemas.enable", 
> false);
> converter.configure(props, true);
> BigInteger value = BigInteger.valueOf(Long.MAX_VALUE).add(new 
> BigInteger("1"));
> String msg = value.toString();
> SchemaAndValue schemaAndValue = converter.toConnectData(TOPIC, 
> msg.getBytes());
> assertNull(schemaAndValue.schema());
> assertEquals(value, schemaAndValue.value());
> {code}
>  
>  Fails with:
>  
> {code:java}
> expected:<9223372036854775808> but was:<-9223372036854775808>
> Expected :9223372036854775808
> Actual :-9223372036854775808
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Double for schema-less case

2020-09-01 Thread Oleksandr Diachenko (Jira) 
Oleksandr Diachenko created KAFKA-10457:
---

 Summary: JsonConverter.toConnectData trims BigInteger to Double 
for schema-less case
 Key: KAFKA-10457
 URL: https://issues.apache.org/jira/browse/KAFKA-10457
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko
 Fix For: 2.7.0


 

When _JsonConverter_ is configured with _schemas.enable=false_ and value, 
exceeding _Double_ is passed, the result is incorrect since the converter trims 
it to _Double:_
{code:java}
Map props = Collections.singletonMap("schemas.enable", false);
converter.configure(props, true);
BigInteger value = BigInteger.valueOf(Long.MAX_VALUE).add(new BigInteger("1"));
String msg = value.toString();
SchemaAndValue schemaAndValue = converter.toConnectData(TOPIC, msg.getBytes());
assertNull(schemaAndValue.schema());
assertEquals(value, schemaAndValue.value());
{code}
 

 Fails with:

 
{code:java}
expected:<9223372036854775808> but was:<-9223372036854775808>
Expected :9223372036854775808
Actual :-9223372036854775808
{code}
 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-10439) Connect's Values class loses precision for integers, larger than 64 bits

2020-08-26 Thread Oleksandr Diachenko (Jira) 
Oleksandr Diachenko created KAFKA-10439:
---

 Summary: Connect's Values class loses precision for integers, 
larger than 64 bits
 Key: KAFKA-10439
 URL: https://issues.apache.org/jira/browse/KAFKA-10439
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko
 Fix For: 2.7.0


The `org.apache.kafka.connect.data.Values#parse` method parses integers, which 
are larger than `Long.MAX_VALUE` as `double` with `

Schema.FLOAT64_SCHEMA`.

 

That means it loses precision for these larger integers.

For example:
{code:java}
SchemaAndValue schemaAndValue = Values.parseString("9223372036854775808");
{code}
returns:
{code:java}
SchemaAndValue{schema=Schema{FLOAT64}, value=9.223372036854776E18}
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-8774) Connect REST API exposes plaintext secrets in tasks endpoint

2019-08-08 Thread Oleksandr Diachenko (JIRA) 
Oleksandr Diachenko created KAFKA-8774:
--

 Summary: Connect REST API exposes plaintext secrets in tasks 
endpoint
 Key: KAFKA-8774
 URL: https://issues.apache.org/jira/browse/KAFKA-8774
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Affects Versions: 2.3.0
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko


I have configured a Connector to use externalized secrets, and the following 
endpoint returns secrets in the externalized form: 
{code:java}
curl localhost:8083/connectors/foobar|jq
{code}
{code:java}
{
"name": "foobar",
"config": {

"connector.class": "io.confluent.connect.s3.S3SinkConnector",
...
"consumer.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"${file:/some/secret/path/secrets.properties:kafka.api.key}\" 
password=\"${file:/some/secret/path/secrets.properties:kafka.api.secret}\";",
"admin.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"${file:/some/secret/path/secrets.properties:kafka.api.key}\" 
password=\"${file:/some/secret/path/secrets.properties:kafka.api.secret}\";",
"consumer.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"${file:/some/secret/path/secrets.properties:kafka.api.key}\" 
password=\"${file:/some/secret/path/secrets.properties:kafka.api.secret}\";",
"producer.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"${file:/some/secret/path/secrets.properties:kafka.api.key}\" 
password=\"${file:/some/secret/path/secrets.properties:kafka.api.secret}\";",
"producer.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"${file:/some/secret/path/secrets.properties:kafka.api.key}\" 
password=\"${file:/some/secret/path/secrets.properties:kafka.api.secret}\";",
...
},
"tasks": [

{ "connector": "foobar", "task": 0 }

],
"type": "sink"
}{code}
But another endpoint returns secrets in plain text:
{code:java}
curl localhost:8083/connectors/foobar/tasks|jq
{code}
{code:java}
[
  {
"id": {
  "connector": "lcc-kgkpm",
  "task": 0
},
"config": {
  "connector.class": "io.confluent.connect.s3.S3SinkConnector",
  ...
  "errors.log.include.messages": "true",
  "flush.size": "1000",
  "consumer.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"OOPS\" password=\"SURPRISE\";",
  "admin.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"OOPS\" password=\"SURPRISE\";",
  "consumer.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"OOPS\" password=\"SURPRISE\";",
  "producer.override.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"OOPS\" password=\"SURPRISE\";",
  "producer.sasl.jaas.config": 
"org.apache.kafka.common.security.plain.PlainLoginModule required 
username=\"OOPS\" password=\"SURPRISE\";",
  ...
}
  }
]
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Updated] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-8418:
---
Description: 
I am getting an error while running Kafka tests:

{code}
Traceback (most recent call last): File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 132, in run data = self.run_test() File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 189, in run_test return self.test_context.function(self.test) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/tests/connect/connect_rest_test.py",
 line 89, in test_rest_api assert set([connector_plugin['class'] for 
connector_plugin in self.cc.list_connector_plugins()]) == 
\{self.FILE_SOURCE_CONNECTOR, self.FILE_SINK_CONNECTOR} File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 218, in list_connector_plugins return self._rest('/connector-plugins/', 
node=node) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 234, in _rest raise ConnectRestError(resp.status_code, resp.text, 
resp.url) ConnectRestError
{code}

>From the logs, I see two messages:
{code}
[2019-05-23 16:09:59,373] INFO REST server listening at 
http://172.31.39.205:8083/, advertising URL http://worker1:8083/ 
(org.apache.kafka.connect.runtime.rest.RestServer)
{code}
and {code}
[2019-05-23 16:10:00,738] INFO REST resources initialized; server is started 
and ready to handle requests (org.apache.kafka.connect.runtime.rest.RestServer)
{code}

 it takes 1365 ms to actually load REST resources, but the test is waiting on a 
port to be listening. 

  was:
I am getting an error while running Kafka tests:

{code}

Traceback (most recent call last): File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 132, in run data = self.run_test() File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 189, in run_test return self.test_context.function(self.test) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/tests/connect/connect_rest_test.py",
 line 89, in test_rest_api assert set([connector_plugin['class'] for 
connector_plugin in self.cc.list_connector_plugins()]) == 
\{self.FILE_SOURCE_CONNECTOR, self.FILE_SINK_CONNECTOR} File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 218, in list_connector_plugins return self._rest('/connector-plugins/', 
node=node) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 234, in _rest raise ConnectRestError(resp.status_code, resp.text, 
resp.url) ConnectRestError

{code}


> Connect System tests are not waiting for REST resources to be registered
> 
>
> Key: KAFKA-8418
> URL: https://issues.apache.org/jira/browse/KAFKA-8418
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 2.2.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.3.0
>
>
> I am getting an error while running Kafka tests:
> {code}
> Traceback (most recent call last): File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
>  line 132, in run data = self.run_test() File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
>  line 189, in run_test return self.test_context.function(self.test) File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/tests/connect/connect_rest_test.py",
>  line 89, in test_rest_api assert set([connector_plugin['class'] for 
> connector_plugin in self.cc.list_connector_plugins()]) == 
> \{self.FILE_SOURCE_CONNECTOR, self.FILE_SINK_CONNECTOR} File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
>  line 218, in list_connector_plugins return self._rest('/connector-plugins/', 
> node=node) File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
>  line 234, in _rest raise ConnectRestError(resp.status_code, resp.text, 
> resp.url) ConnectRestError
> {code}
> From the logs, I see two messages:
> {code}
>

[jira] [Updated] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-8418:
---
Description: 
I am getting an error while running Kafka tests:

{code}

Traceback (most recent call last): File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 132, in run data = self.run_test() File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
 line 189, in run_test return self.test_context.function(self.test) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/tests/connect/connect_rest_test.py",
 line 89, in test_rest_api assert set([connector_plugin['class'] for 
connector_plugin in self.cc.list_connector_plugins()]) == 
\{self.FILE_SOURCE_CONNECTOR, self.FILE_SINK_CONNECTOR} File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 218, in list_connector_plugins return self._rest('/connector-plugins/', 
node=node) File 
"/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
 line 234, in _rest raise ConnectRestError(resp.status_code, resp.text, 
resp.url) ConnectRestError

{code}

> Connect System tests are not waiting for REST resources to be registered
> 
>
> Key: KAFKA-8418
> URL: https://issues.apache.org/jira/browse/KAFKA-8418
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 2.2.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.3.0
>
>
> I am getting an error while running Kafka tests:
> {code}
> Traceback (most recent call last): File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
>  line 132, in run data = self.run_test() File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.7.5-py2.7.egg/ducktape/tests/runner_client.py",
>  line 189, in run_test return self.test_context.function(self.test) File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/tests/connect/connect_rest_test.py",
>  line 89, in test_rest_api assert set([connector_plugin['class'] for 
> connector_plugin in self.cc.list_connector_plugins()]) == 
> \{self.FILE_SOURCE_CONNECTOR, self.FILE_SINK_CONNECTOR} File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
>  line 218, in list_connector_plugins return self._rest('/connector-plugins/', 
> node=node) File 
> "/home/jenkins/workspace/system-test-kafka_5.3.x/kafka/tests/kafkatest/services/connect.py",
>  line 234, in _rest raise ConnectRestError(resp.status_code, resp.text, 
> resp.url) ConnectRestError
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-8418:
---
Fix Version/s: 2.3.0

> Connect System tests are not waiting for REST resources to be registered
> 
>
> Key: KAFKA-8418
> URL: https://issues.apache.org/jira/browse/KAFKA-8418
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 2.2.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.3.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-8418:
---
Affects Version/s: 2.2.0

> Connect System tests are not waiting for REST resources to be registered
> 
>
> Key: KAFKA-8418
> URL: https://issues.apache.org/jira/browse/KAFKA-8418
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 2.2.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-8418:
---
Component/s: KafkaConnect

> Connect System tests are not waiting for REST resources to be registered
> 
>
> Key: KAFKA-8418
> URL: https://issues.apache.org/jira/browse/KAFKA-8418
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KAFKA-8418) Connect System tests are not waiting for REST resources to be registered

2019-05-23 Thread Oleksandr Diachenko (JIRA) 
Oleksandr Diachenko created KAFKA-8418:
--

 Summary: Connect System tests are not waiting for REST resources 
to be registered
 Key: KAFKA-8418
 URL: https://issues.apache.org/jira/browse/KAFKA-8418
 Project: Kafka
  Issue Type: Bug
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-7799) Fix flaky test RestServerTest.testCORSEnabled

2019-02-19 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-7799:
---
Fix Version/s: 2.1.2
   2.0.2
   2.2.0

> Fix flaky test RestServerTest.testCORSEnabled
> -
>
> Key: KAFKA-7799
> URL: https://issues.apache.org/jira/browse/KAFKA-7799
> Project: Kafka
>  Issue Type: Test
>  Components: KafkaConnect
>Reporter: Jason Gustafson
>Assignee: Jason Gustafson
>Priority: Major
> Fix For: 2.2.0, 2.0.2, 2.3.0, 2.1.2
>
>
> Starting to see this failure quite a lot, locally and on jenkins:
> {code}
> org.apache.kafka.connect.runtime.rest.RestServerTest.testCORSEnabled
> Failing for the past 7 builds (Since Failed#18600 )
> Took 0.7 sec.
> Error Message
> java.lang.AssertionError: expected: but was:
> Stacktrace
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> org.apache.kafka.connect.runtime.rest.RestServerTest.checkCORSRequest(RestServerTest.java:221)
>   at 
> org.apache.kafka.connect.runtime.rest.RestServerTest.testCORSEnabled(RestServerTest.java:84)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:68)
>   at 
> org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:326)
>   at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:89)
>   at 
> org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:97)
> {code}
> If it helps, I see an uncaught exception in the stdout:
> {code}
> [2019-01-08 19:35:23,664] ERROR Uncaught exception in REST call to 
> /connector-plugins/FileStreamSource/validate 
> (org.apache.kafka.connect.runtime.rest.errors.ConnectExceptionMapper:61)
> javax.ws.rs.NotFoundException: HTTP 404 Not Found
>   at 
> org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:274)
>   at org.glassfish.jersey.internal.Errors$1.call(Errors.java:272)
>   at org.glassfish.jersey.internal.Errors$1.call(Errors.java:268)
>   at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
>   at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
>   at org.glassfish.jersey.internal.Errors.process(Errors.java:268)
>   at 
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:289)
>   at 
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:256)
>   at 
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

2018-12-20 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-7759:
---
Description: 
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented , so it should be disabled.

  was:
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented and poses potential security vulnerability, so it 
should be disabled.


> Disable WADL output on OPTIONS method in Connect REST
> -
>
> Key: KAFKA-7759
> URL: https://issues.apache.org/jira/browse/KAFKA-7759
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Major
> Fix For: 2.2.0
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:java}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> It was never documented , so it should be disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

2018-12-20 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-7759:
---
Description: 
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented, so in order to remove unintended behavior, WADL output 
should be disabled.

  was:
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented, so in order to remove unintended behaviour, WADL 
output should be disabled.


> Disable WADL output on OPTIONS method in Connect REST
> -
>
> Key: KAFKA-7759
> URL: https://issues.apache.org/jira/browse/KAFKA-7759
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Major
> Fix For: 2.2.0
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:java}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> It was never documented, so in order to remove unintended behavior, WADL 
> output should be disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

2018-12-20 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-7759:
---
Description: 
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented, so in order to remove unintended behaviour, WADL 
output should be disabled.

  was:
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented, so in order to remove unintended bwhaviour it should 
be disabled.


> Disable WADL output on OPTIONS method in Connect REST
> -
>
> Key: KAFKA-7759
> URL: https://issues.apache.org/jira/browse/KAFKA-7759
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Major
> Fix For: 2.2.0
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:java}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> It was never documented, so in order to remove unintended behaviour, WADL 
> output should be disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

2018-12-20 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko updated KAFKA-7759:
---
Description: 
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented, so in order to remove unintended bwhaviour it should 
be disabled.

  was:
Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:java}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented , so it should be disabled.


> Disable WADL output on OPTIONS method in Connect REST
> -
>
> Key: KAFKA-7759
> URL: https://issues.apache.org/jira/browse/KAFKA-7759
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Major
> Fix For: 2.2.0
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:java}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> It was never documented, so in order to remove unintended bwhaviour it should 
> be disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (KAFKA-7715) Connect should have a parameter to disable WADL output for OPTIONS method

2018-12-19 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko resolved KAFKA-7715.

Resolution: Won't Fix

Related KIP(KIP-404) was discarded, reported a bug - 
https://issues.apache.org/jira/browse/KAFKA-7759

> Connect should have a parameter to disable WADL output for OPTIONS method
> -
>
> Key: KAFKA-7715
> URL: https://issues.apache.org/jira/browse/KAFKA-7715
> Project: Kafka
>  Issue Type: Improvement
>  Components: config, security
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.1.1
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:bash}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> This can be a potential vulnerability, so it makes sense to have a 
> configuration parameter, which disables WADL output.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

2018-12-19 Thread Oleksandr Diachenko (JIRA) 
Oleksandr Diachenko created KAFKA-7759:
--

 Summary: Disable WADL output on OPTIONS method in Connect REST
 Key: KAFKA-7759
 URL: https://issues.apache.org/jira/browse/KAFKA-7759
 Project: Kafka
  Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko
 Fix For: 2.2.0


Currently, Connect REST API exposes WADL output on OPTIONS method:
{code}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}
It was never documented and poses potential security vulnerability, so it 
should be disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (KAFKA-7715) Connect should have a parameter to disable WADL output for OPTIONS method

2018-12-12 Thread Oleksandr Diachenko (JIRA) 


 [ 
https://issues.apache.org/jira/browse/KAFKA-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Diachenko reassigned KAFKA-7715:
--

Assignee: Oleksandr Diachenko

> Connect should have a parameter to disable WADL output for OPTIONS method
> -
>
> Key: KAFKA-7715
> URL: https://issues.apache.org/jira/browse/KAFKA-7715
> Project: Kafka
>  Issue Type: Improvement
>  Components: config, security
>Affects Versions: 2.1.0
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Critical
> Fix For: 2.1.1
>
>
> Currently, Connect REST API exposes WADL output on OPTIONS method:
> {code:bash}
> curl -i -X OPTIONS http://localhost:8083/connectors
> HTTP/1.1 200 OK
> Date: Fri, 07 Dec 2018 22:51:53 GMT
> Content-Type: application/vnd.sun.wadl+xml
> Allow: HEAD,POST,GET,OPTIONS
> Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
> Content-Length: 1331
> Server: Jetty(9.4.12.v20180830)
> 
> http://wadl.dev.java.net/2009/02;>
> http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
> 2018-04-10 07:34:57"/>
> 
> http://localhost:8083/application.wadl/xsd0.xsd;>
> 
> 
> 
> http://localhost:8083/;>
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema; name="forward" 
> style="query" type="xs:boolean"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> This can be a potential vulnerability, so it makes sense to have a 
> configuration parameter, which disables WADL output.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KAFKA-7715) Connect should have a parameter to disable WADL output for OPTIONS method

2018-12-07 Thread Oleksandr Diachenko (JIRA) 
Oleksandr Diachenko created KAFKA-7715:
--

 Summary: Connect should have a parameter to disable WADL output 
for OPTIONS method
 Key: KAFKA-7715
 URL: https://issues.apache.org/jira/browse/KAFKA-7715
 Project: Kafka
  Issue Type: Improvement
  Components: config, security
Affects Versions: 2.1.0
Reporter: Oleksandr Diachenko
 Fix For: 2.1.1


Currently, Connect REST API exposes WADL output on OPTIONS method:
{code:bash}
curl -i -X OPTIONS http://localhost:8083/connectors
HTTP/1.1 200 OK
Date: Fri, 07 Dec 2018 22:51:53 GMT
Content-Type: application/vnd.sun.wadl+xml
Allow: HEAD,POST,GET,OPTIONS
Last-Modified: Fri, 07 Dec 2018 14:51:53 PST
Content-Length: 1331
Server: Jetty(9.4.12.v20180830)


http://wadl.dev.java.net/2009/02;>
http://jersey.java.net/; jersey:generatedBy="Jersey: 2.27 
2018-04-10 07:34:57"/>

http://localhost:8083/application.wadl/xsd0.xsd;>



http://localhost:8083/;>



http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








http://www.w3.org/2001/XMLSchema; name="forward" style="query" 
type="xs:boolean"/>








{code}

This can be a potential vulnerability, so it makes sense to have a 
configuration parameter, which disables WADL output.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)