d it be alright to include the exception message,
but not the entire stack trace, in the response for requests to view the
status of a connector or task?
Cheers,
Chris
On Wed, May 6, 2020 at 12:07 PM Connor Penhale
wrote:
> Hi Chris,
>
> Apologies for the nam
ncludes (but is not limited to) the REST API and worker
configuration properties, so it might be worth briefly summarizing the
scope of your proposed changes in that section (something like "We plan on
adding a new worker config named that will affect the REST API under
".
Cheer
;s not really necessary to describe the internal implementation in the
KIP, but since you mentioned it, it's probably worth considering using the
current ExceptionMapper class with a different configuration rather than
creating a new one.
best,
Colin
On Mon, Apr 13, 2020, at 0
to the /connectors/file-source/status
endpoint.
I was wondering if you wanted to include these kinds of stack traces as
part of the KIP, as opposed to uncaught exceptions that result in a 500
error from the REST API.
Cheers,
Chris
On Wed, Apr 8, 2020 at 9:51 AM Connor
?
Thanks!
Connor
On 4/6/20, 9:03 AM, "Connor Penhale" wrote:
Hi Colin,
We did not find a specific security vulnerability. Our customer had
auditors in their environment, and they identified Kafka Connect as out of
compliance with their particular standards, something that h
I only mention PCI-DSS as this was the kind of environment my customer had that
was making the request for being able to tune the response.
Thanks!
Connor
---
Connor Penhale | Enterprise Architect, OpenLogic (https://openlogic.com/)
Perforce (https://www.perforce.com/)
Support: +1 866.399.6736
ct on users of the Connect framework.
Thanks for the KIP, looking forward to seeing this happen!
Cheers,
Chris
On Thu, Apr 2, 2020 at 11:01 AM Connor Penhale
wrote:
> Hello All!
>
> I’ve created the following KIP:
>
https://cwiki.apache.o
2.0, but I would be
working on Kafka Connect in 2.6 to get this behavior changed to the community’s
preference.
Looking forward to working with everyone!
Thanks!
Connor
---
Connor Penhale | Enterprise Architect, OpenLogic (https://openlogic.com/)
Perforce (https://www.perforce.com/)
Support: +1
t from the Jira project.
You’ll have to create a user in the wiki and then let us know the I’d so we can
give you edit permission (so you can create the KIP).
Thanks!
-John
On Tue, Mar 31, 2020, at 13:38, Connor Penhale wrote:
> Hi Chris,
>
> No problem! My customer
l only be viable for inclusion in future releases. The
earliest possible release that such changes could be included in would be
2.6, since the KIP deadline has already passed for the upcoming 2.5 release.
Hope this helps!
Cheers,
Chris
On Tue, Mar 31, 2020 at 11:12
there’s anything I can do to help
this feature become part of Kafka! We have a customer that really wants this
feature, because their security team for PCI-DSS is unhappy with how Kafka
Connect handles things like malformed JSON, as an example. Eager to work with
everyone!
Thanks!
Connor
Connor
Connor Penhale created KAFKA-9766:
-
Summary: Suppress detailed responses for security-sensitive
(PCI-DSS) environments
Key: KAFKA-9766
URL: https://issues.apache.org/jira/browse/KAFKA-9766
Project
12 matches
Mail list logo